summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Dooks <ben-linux@fluff.org>2010-05-26 14:42:21 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2010-05-27 09:12:41 -0700
commit796a8e423ac8afe9e98ad96e668f50142bdd7825 (patch)
tree1ecf3e0e86c41695e24bc0102c686aedbca98c41
parenta13c1868aa60ae7a2516b8d00ee8873dea587581 (diff)
downloadlinux-3.10-796a8e423ac8afe9e98ad96e668f50142bdd7825.tar.gz
linux-3.10-796a8e423ac8afe9e98ad96e668f50142bdd7825.tar.bz2
linux-3.10-796a8e423ac8afe9e98ad96e668f50142bdd7825.zip
gpiolib: make gpiochip_add() show a better error message
The current message, 'not registered' is confusing as it implies it was not registered with something, whereas printing 'failed to register' implies it was the gpiochip_add() call that did not work correctly. Signed-off-by: Ben Dooks <ben-linux@fluff.org> Cc: David Brownell <david-b@pacbell.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-rw-r--r--drivers/gpio/gpiolib.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
index 05019c15a86..362a613d266 100644
--- a/drivers/gpio/gpiolib.c
+++ b/drivers/gpio/gpiolib.c
@@ -1106,7 +1106,7 @@ unlock:
fail:
/* failures here can mean systems won't boot... */
if (status)
- pr_err("gpiochip_add: gpios %d..%d (%s) not registered\n",
+ pr_err("gpiochip_add: gpios %d..%d (%s) failed to register\n",
chip->base, chip->base + chip->ngpio - 1,
chip->label ? : "generic");
return status;