From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: barebox@lists.infradead.org
Subject: [PATCH 3/4] OF: gpio: Silence error message on -EPROBE_DEFER
Date: Fri, 10 Apr 2015 03:02:45 +0200 [thread overview]
Message-ID: <1428627766-17178-4-git-send-email-sebastian.hesselbarth@gmail.com> (raw)
In-Reply-To: <1428627766-17178-1-git-send-email-sebastian.hesselbarth@gmail.com>
With deferred probing, -EPROBE_DEFER is not worth spilling an error.
Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
---
Cc: barebox@lists.infradead.org
---
drivers/of/of_gpio.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/of/of_gpio.c b/drivers/of/of_gpio.c
index 6738a220a5a3..470ccfa1ba77 100644
--- a/drivers/of/of_gpio.c
+++ b/drivers/of/of_gpio.c
@@ -39,8 +39,9 @@ int of_get_named_gpio_flags(struct device_node *np, const char *propname,
ret = gpio_get_num(dev, out_args.args[0]);
if (ret < 0) {
- pr_err("%s: unable to get gpio num of device %s: %d\n",
- __func__, dev_name(dev), ret);
+ if (ret != -EPROBE_DEFER)
+ pr_err("%s: unable to get gpio num of device %s: %d\n",
+ __func__, dev_name(dev), ret);
return ret;
}
--
2.1.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-04-10 1:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 1:02 [PATCH 0/4] Introduce deferred probing Sebastian Hesselbarth
2015-04-10 1:02 ` [PATCH 1/4] base: " Sebastian Hesselbarth
2015-04-13 6:54 ` Sascha Hauer
2015-04-13 14:26 ` Sebastian Hesselbarth
2015-04-10 1:02 ` [PATCH 2/4] gpio: Return -EPROBE_DEFER on gpio_get_num() Sebastian Hesselbarth
2015-04-10 1:02 ` Sebastian Hesselbarth [this message]
2015-04-10 1:02 ` [PATCH 4/4] led: gpio: Properly deal with deferred probing Sebastian Hesselbarth
2015-04-13 8:14 ` [PATCH 0/4] Introduce " Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1428627766-17178-4-git-send-email-sebastian.hesselbarth@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox