summaryrefslogtreecommitdiffstats
path: root/common
diff options
context:
space:
mode:
authorHarald Welte <laforge@gnumonks.org>2016-02-17 19:29:46 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2016-02-18 12:57:44 +0100
commit2b480855e60fe40a352a6e6b532fd311d0ea887f (patch)
tree526db14fa3c26782693794a337ad818608526984 /common
parenta29f5e9d50aa5c5c61a5b17188a799740545ded8 (diff)
downloadbarebox-2b480855e60fe40a352a6e6b532fd311d0ea887f.tar.gz
barebox-2b480855e60fe40a352a6e6b532fd311d0ea887f.tar.xz
Print error message if of_state_fixup() fails
If of_state_fixup() fails for some reason, boot/bootm will fail, too However, it is completely unclear where the error has happened, and to the user it rather seems like the kernel device tree loaded from some file was broken/corrupt, not that in fact some fixup routine was failing. Adding a meaningful error message can help debugging significantly. Signed-off-by: Harald Welte <laforge@gnumonks.org> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'common')
-rw-r--r--common/state.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/common/state.c b/common/state.c
index 3e95efd911..b55b1503bd 100644
--- a/common/state.c
+++ b/common/state.c
@@ -999,6 +999,7 @@ static int of_state_fixup(struct device_node *root, void *ctx)
return 0;
out:
+ dev_err(&state->dev, "error fixing up device tree with boot state\n");
of_delete_node(new_node);
return ret;
}