From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Levente Révész" <levente.revesz@eilabs.com>
Cc: Martyn Welch <martyn.welch@collabora.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Haibo Chen <haibo.chen@nxp.com>, Puyou Lu <puyou.lu@gmail.com>,
Justin Chen <justinpopo6@gmail.com>,
Andrey Gusakov <andrey.gusakov@cogentembedded.com>,
Nate Drude <nate.d@variscite.com>,
linux-gpio@vger.kernel.org, Peter Robinson <pbrobinson@gmail.com>
Subject: Re: [RFC PATCH 0/3] gpio: pca953x: Redesign handling of chip types
Date: Fri, 3 Feb 2023 13:32:33 +0200 [thread overview]
Message-ID: <Y9zw0Xy2ctkQ383S@smile.fi.intel.com> (raw)
In-Reply-To: <8c9dc414-9c15-26db-fcae-233c5ca0a171@eilabs.com>
On Fri, Feb 03, 2023 at 11:40:50AM +0100, Levente Révész wrote:
> On 02/02/2023 16.14, Andy Shevchenko wrote:
> > On Thu, Feb 02, 2023 at 05:12:22PM +0200, Andy Shevchenko wrote:
> >> Now as I'm thinking more of your nice job, it may be less effort to everybody
> >> if you start from moving the driver to be a real pin control driver united with
> >> GPIO handling.
>
> I will look into this, it will probably take a few weeks to come up with
> something presentable.
You have that time because the current series marked as RFC and even
if it had been ready it would have not been applied due to release schedule
(we are now at almost v6.2-rc7 and in two and half weeks we expect
the release to come, so it means you have ~6 weeks of time).
> Thank you for your review so far!
You are welcome!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2023-02-03 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 20:59 [RFC PATCH 0/3] gpio: pca953x: Redesign handling of chip types Levente Révész
2023-01-30 21:32 ` Andy Shevchenko
2023-02-02 15:12 ` Andy Shevchenko
2023-02-02 15:14 ` Andy Shevchenko
2023-02-03 10:40 ` Levente Révész
2023-02-03 11:32 ` Andy Shevchenko [this message]
2023-02-03 12: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=Y9zw0Xy2ctkQ383S@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andrey.gusakov@cogentembedded.com \
--cc=brgl@bgdev.pl \
--cc=haibo.chen@nxp.com \
--cc=justinpopo6@gmail.com \
--cc=levente.revesz@eilabs.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=martyn.welch@collabora.com \
--cc=nate.d@variscite.com \
--cc=pbrobinson@gmail.com \
--cc=puyou.lu@gmail.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