[U-Boot] [RFC PATCH 14/21] dm: sandbox: sf: Tidy up the error handling in sandbox_sf_probe()
Simon Glass
sjg at chromium.org
Sat Jan 17 00:15:36 CET 2015
Use a single exit point when we have an error and add debugging there.
Signed-off-by: Simon Glass <sjg at chromium.org>
---
drivers/mtd/spi/sandbox.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/spi/sandbox.c b/drivers/mtd/spi/sandbox.c
index 3024b98..106dda9 100644
--- a/drivers/mtd/spi/sandbox.c
+++ b/drivers/mtd/spi/sandbox.c
@@ -141,8 +141,10 @@ static int sandbox_sf_probe(struct udevice *dev)
assert(bus->seq != -1);
if (bus->seq < CONFIG_SANDBOX_SPI_MAX_BUS)
spec = state->spi[bus->seq][cs].spec;
- if (!spec)
- return -ENOENT;
+ if (!spec) {
+ ret = -ENOENT;
+ goto error;
+ }
file = strchr(spec, ':');
if (!file) {
@@ -196,6 +198,7 @@ static int sandbox_sf_probe(struct udevice *dev)
return 0;
error:
+ debug("%s: Got error %d\n", __func__, ret);
return ret;
}
--
2.2.0.rc0.207.ga3a616c
More information about the U-Boot
mailing list