From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] gpio: add sloppy logic analyzer using polling
Date: Mon, 22 Nov 2021 14:33:28 +0200 [thread overview]
Message-ID: <YZuOGAxO5ZslW5vB@smile.fi.intel.com> (raw)
In-Reply-To: <YZuKyEcsXb8dwiHG@ninjato>
On Mon, Nov 22, 2021 at 01:19:20PM +0100, Wolfram Sang wrote:
...
> > > > > + if (ret < 0) {
> > > >
> > > > > + dev_err(dev, "error naming the GPIOs: %d\n", ret);
> > > > > + return ret;
> > > > > + }
> > > >
> > > > Perhaps
> > > >
> > > > return dev_err_probe() ?
> > >
> > > Reading strings from DT can be deferred? I don't think so.
> >
> > There is a new development, i.e. the documentation for dev_err_probe()
> > is going to be amended to allow this. But I can't quickly find a patch
> > in mailing list with the related discussion.
>
> I still don't get this one, so if there is new development and you have
> a pointer, I'd be glad to hear about it. Otherwise we can fix it
> incrementally later.
See 7065f92255bb ("driver core: Clarify that dev_err_probe() is OK even w/out
-EPROBE_DEFER").
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-11-22 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 8:33 [PATCH v2 0/1] gpio: add simple logic analyzer using polling Wolfram Sang
2021-09-18 8:33 ` [PATCH v2 1/1] gpio: add sloppy " Wolfram Sang
2021-09-19 20:27 ` Andy Shevchenko
2021-09-20 8:30 ` Wolfram Sang
2021-09-20 8:45 ` Andy Shevchenko
2021-11-22 12:19 ` Wolfram Sang
2021-11-22 12:33 ` Andy Shevchenko [this message]
2021-11-22 15:03 ` Wolfram Sang
2021-09-20 12:15 ` Geert Uytterhoeven
2021-11-22 11:43 ` Wolfram Sang
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=YZuOGAxO5ZslW5vB@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
/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