From: Thierry Reding <thierry.reding@gmail.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Thierry Reding <treding@nvidia.com>
Subject: Re: [rft, PATCH v4 0/3] gpiolib: eventual of_node retirement
Date: Wed, 4 Jan 2023 17:41:46 +0100 [thread overview]
Message-ID: <Y7WsSh6RCNGIgml4@orome> (raw)
In-Reply-To: <20221228092045.80425-1-andriy.shevchenko@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Wed, Dec 28, 2022 at 11:20:42AM +0200, Andy Shevchenko wrote:
> Now that all GPIO library users are converted to use fwnode,
> Drop redundant field from struct gpio_chip and accompanying
> code.
>
> Bart, I prefer this series to go as soon as possible if you
> have no objection. Or even as v6.2 material.
>
> Thierry, can you please test it once again, so we will be sure
> there is no breakage for OF platforms?
Seems to be working fine on at least Jetson TX1, so:
Tested-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-04 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 9:20 [rft, PATCH v4 0/3] gpiolib: eventual of_node retirement Andy Shevchenko
2022-12-28 9:20 ` [PATCH v4 1/3] gpiolib: Introduce gpio_device_get() and gpio_device_put() Andy Shevchenko
2022-12-28 9:20 ` [PATCH v4 2/3] gpiolib: Get rid of not used of_node member Andy Shevchenko
2022-12-28 9:20 ` [PATCH v4 3/3] gpiolib: sort header inclusion alphabetically Andy Shevchenko
2022-12-29 21:20 ` [rft, PATCH v4 0/3] gpiolib: eventual of_node retirement Linus Walleij
2023-01-04 8:51 ` Bartosz Golaszewski
2023-01-04 16:41 ` Thierry Reding [this message]
2023-01-04 16:51 ` Andy Shevchenko
2023-01-05 9:55 ` Thierry Reding
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=Y7WsSh6RCNGIgml4@orome \
--to=thierry.reding@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=dmitry.torokhov@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).