early_init_dt_scan() now takes care of falling back to the built-in DTB,
and printing what it did.
Signed-off-by: Geert Uytterhoeven <ge...@linux-m68k.org>
Cc: Jonas Bonn <jo...@southpole.se>
Cc: li...@lists.openrisc.net
---
arch/openrisc/kernel/setup.c | 6 ------
1 file changed, 6 deletions(-)
diff --git a/arch/openrisc/kernel/setup.c b/arch/openrisc/kernel/setup.c
index 3ca640cd42be..4ec6b07f02b3 100644
--- a/arch/openrisc/kernel/setup.c
+++ b/arch/openrisc/kernel/setup.c
@@ -212,12 +212,6 @@ void __init setup_cpuinfo(void)
void __init or32_early_setup(void *fdt)
{
- if (fdt)
- pr_info("FDT at %p\n", fdt);
- else {
- fdt = &__dtb_start;
- pr_info("Compiled-in FDT at %p\n", fdt);
- }
early_init_devtree(fdt);
}
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
