diff options
author | Florian Fainelli <f.fainelli@gmail.com> | 2015-04-12 23:16:26 +0300 |
---|---|---|
committer | Rob Herring <robh@kernel.org> | 2015-04-15 03:35:43 +0300 |
commit | c954b36e3f5bfdd5aeceba49614a4864d7efec87 (patch) | |
tree | c265c9c7e35492a6f3fd8237f610bb00ed644887 | |
parent | 3712655914530479b424e6f3db2130c48b931a41 (diff) | |
download | linux-c954b36e3f5bfdd5aeceba49614a4864d7efec87.tar.xz |
of/fdt: Remove "reg" data prints from early_init_dt_scan_memory
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@gmail.com>
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Rob Herring <robh@kernel.org>
-rw-r--r-- | drivers/of/fdt.c | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c index 3a896c9aeb74..34bdc4de83d0 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; |