Re: [PATCH] of/fdt: Remove "reg" data prints from early_init_dt_scan_memory

[Rob Herring]

On Sun, Apr 12, 2015 at 3:16 PM, Florian Fainelli <f.fainelli@xxxxxxxxx> wrote:
> Commit 51975db0b7333 ("of/flattree: merge early_init_dt_scan_memory()
> common code") consolidated some code from PowerPC (typically
> big-endian), and ended-up adding a pr_debug() printing reg properties in
> big-endian (DT native) format, not CPU endian.
>
> This debug print suffers from two problems:
> - we only print 4 "reg" values, while there could be more on typical
>   systems having multiple memory ranges
> - we print these 4 "reg" values in FDT endianess, that is big-endian,
>   and these values could be confusing for little-endian configurations
>
> Since we are already printing the base address and size of the memory
> regions parsed by early_init_dt_scan_memory() later in a way that is
> both endian correct, and takes into account arbitrary number of memory
> banks, just remove that part of the debug print.
>
> Suggested-by: Frank Rowand <frowand.list@xxxxxxxxx>
> Signed-off-by: Florian Fainelli <f.fainelli@xxxxxxxxx>
> ---
> Patch against devicetree/next

Applied. Thanks.

Rob

>
>  drivers/of/fdt.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
> index 3a896c9..34bdc4d 100644
> --- a/drivers/of/fdt.c
> +++ b/drivers/of/fdt.c
> @@ -879,8 +879,7 @@ int __init early_init_dt_scan_memory(unsigned long node, const char *uname,
>
>         endp = reg + (l / sizeof(__be32));
>
> -       pr_debug("memory scan node %s, reg size %d, data: %x %x %x %x,\n",
> -           uname, l, reg[0], reg[1], reg[2], reg[3]);
> +       pr_debug("memory scan node %s, reg size %d,\n", uname, l);
>
>         while ((endp - reg) >= (dt_root_addr_cells + dt_root_size_cells)) {
>                 u64 base, size;
> --
> 2.1.0
>
--
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/