From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Alexandre Courbot <gnurou@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] gpiolib: don't bother warning when failing to get gpios
Date: Fri, 29 Nov 2013 13:08:45 +0200 [thread overview]
Message-ID: <20131129110845.GA3942@xps8300> (raw)
In-Reply-To: <CAAVeFuJUWcOKos3ds-ekRv6T0=sU6dtx5M3rQNTGKMDCVj68Eg@mail.gmail.com>
Hi,
On Fri, Nov 29, 2013 at 06:37:35PM +0900, Alexandre Courbot wrote:
> On Fri, Nov 29, 2013 at 6:16 PM, Heikki Krogerus
> > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > index 4e10b10..2f0305e 100644
> > --- a/drivers/gpio/gpiolib.c
> > +++ b/drivers/gpio/gpiolib.c
> > @@ -2434,10 +2434,8 @@ struct gpio_desc *__must_check gpiod_get_index(struct device *dev,
> > desc = gpiod_find(dev, con_id, idx, &flags);
> > }
> >
> > - if (IS_ERR(desc)) {
> > - dev_warn(dev, "lookup for GPIO %s failed\n", con_id);
> > + if (IS_ERR(desc))
> > return desc;
> > - }
> >
> > status = gpiod_request(desc, con_id);
>
> I kind of agree with the logic that motivates this patch, but how
> about turning this warning into dev_dbg() instead so that people who
> wish so can still continue using it?
Sure, I'll send v2 of this and do just that.
Thanks,
--
heikki
next prev parent reply other threads:[~2013-11-29 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 9:16 [PATCH] gpiolib: don't bother warning when failing to get gpios Heikki Krogerus
2013-11-29 9:37 ` Alexandre Courbot
2013-11-29 11:08 ` Heikki Krogerus [this message]
2013-11-29 13:33 ` Linus Walleij
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=20131129110845.GA3942@xps8300 \
--to=heikki.krogerus@linux.intel.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).