From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 2/2] gpiolib: check the 'ngpios' property in core gpiolib code
Date: Fri, 12 Nov 2021 17:07:11 +0200 [thread overview]
Message-ID: <YY6DHw6q/1B3NpMC@smile.fi.intel.com> (raw)
In-Reply-To: <CAMRc=MdtuDVnBMWHuTYUC7e65s8GsYrPnRv0zcmWGJwEQfmuSw@mail.gmail.com>
On Fri, Nov 12, 2021 at 03:48:34PM +0100, Bartosz Golaszewski wrote:
> On Thu, Nov 11, 2021 at 9:47 PM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
...
> Will do. Just a note: some drivers that parse the ngpios property will
> need to continue doing it themselves as they have additional
> requirements from the value (limited max value, needs to be multiple
> of 8, etc.) on the read value. For those that are obvious, we can
> start converting them after this patch lands.
Sure! No objections from my side.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-11-12 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 20:25 [PATCH 1/2] gpiolib: improve coding style for local variables Bartosz Golaszewski
2021-11-11 20:25 ` [PATCH RFC 2/2] gpiolib: check the 'ngpios' property in core gpiolib code Bartosz Golaszewski
2021-11-11 20:31 ` Linus Walleij
2021-11-11 20:47 ` Andy Shevchenko
2021-11-12 14:48 ` Bartosz Golaszewski
2021-11-12 15:07 ` Andy Shevchenko [this message]
2021-11-11 20:29 ` [PATCH 1/2] gpiolib: improve coding style for local variables Linus Walleij
2021-11-11 20:30 ` 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=YY6DHw6q/1B3NpMC@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@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