[PATCH] of: add some debugging statements if initrd isn't found
From: Andres Salomon <hidden>
Date: 2012-02-03 22:24:08
Also in:
lkml
Subsystem:
open firmware and flattened device tree, the rest · Maintainers:
Rob Herring, Saravana Kannan, Linus Torvalds
While debugging initrd problems in a FDT blob, it's nice to both terminate the "Looking for initrd properties... " with a newline, as well as letting us know which property wasn't found. Signed-off-by: Andres Salomon <redacted> --- drivers/of/fdt.c | 8 ++++++-- 1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/of/fdt.c b/drivers/of/fdt.c
index ea2bd1b..92234f7 100644
--- a/drivers/of/fdt.c
+++ b/drivers/of/fdt.c@@ -561,13 +561,17 @@ void __init early_init_dt_check_for_initrd(unsigned long node) pr_debug("Looking for initrd properties... "); prop = of_get_flat_dt_prop(node, "linux,initrd-start", &len); - if (!prop) + if (!prop) { + pr_debug("couldn't find linux,initrd-start\n"); return; + } start = of_read_ulong(prop, len/4); prop = of_get_flat_dt_prop(node, "linux,initrd-end", &len); - if (!prop) + if (!prop) { + pr_debug("couldn't find linux,initrd-end\n"); return; + } end = of_read_ulong(prop, len/4); early_init_dt_setup_initrd_arch(start, end);
--
1.7.2.5