summaryrefslogtreecommitdiffstats
path: root/mm
diff options
context:
space:
mode:
authorFlorian Fainelli <f.fainelli@gmail.com>2015-04-12 13:16:26 -0700
committerRob Herring <robh@kernel.org>2015-04-14 19:35:43 -0500
commitc954b36e3f5bfdd5aeceba49614a4864d7efec87 (patch)
treec265c9c7e35492a6f3fd8237f610bb00ed644887 /mm
parent3712655914530479b424e6f3db2130c48b931a41 (diff)
downloadlinux-stable-c954b36e3f5bfdd5aeceba49614a4864d7efec87.tar.gz
linux-stable-c954b36e3f5bfdd5aeceba49614a4864d7efec87.tar.bz2
linux-stable-c954b36e3f5bfdd5aeceba49614a4864d7efec87.zip
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>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions