Re: [PATCH] mm/memblock: add debug output for the memblock_add

From: Alexander Kuleshov
Date: Wed Apr 01 2015 - 03:21:30 EST


2015-04-01 5:38 GMT+06:00 Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>:
> On Sat, 28 Mar 2015 23:08:03 +0600 Alexander Kuleshov <kuleshovmail@xxxxxxxxx> wrote:
>
> I guess this should be "memblock_add:". That's what
> memblock_reserve_region() does?
>
> --- a/mm/memblock.c~mm-memblock-add-debug-output-for-the-memblock_add-fix
> +++ a/mm/memblock.c
> @@ -587,7 +587,7 @@ static int __init_memblock memblock_add_
> {
> struct memblock_type *_rgn = &memblock.memory;
>
> - memblock_dbg("memblock_memory: [%#016llx-%#016llx] flags %#02lx %pF\n",
> + memblock_dbg("memblock_add: [%#016llx-%#016llx] flags %#02lx %pF\n",
> (unsigned long long)base,
> (unsigned long long)base + size - 1,
> flags, (void *)_RET_IP_);
> _
>

Yes, it is much cleaner. Thank you Andrew.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/