From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
linux-gpio@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: [PATCH v1 0/3] gpiolib: Avpid modifying GPIO chip fwnode
Date: Mon, 3 Jul 2023 15:18:35 +0300 [thread overview]
Message-ID: <20230703121838.70898-1-andriy.shevchenko@linux.intel.com> (raw)
Ideally the GPIO chip data structure has to be constant.
In real life it's not true, but we can make it closer to
that. Hence the series.
Benjamin, would be nice it you can perform regression test for your
case.
Bart, the idea is that this series has to land immediately after
v6.5-rc1 is out so we will have longer time to fix any downsides
and regressions found, if any.
Andy Shevchenko (3):
gpiolib: of: Don't use GPIO chip fwnode in of_gpiochip_*()
gpiolib: acpi: Don't use GPIO chip fwnode in acpi_gpiochip_find()
gpiolib: Do not alter GPIO chip fwnode member
drivers/gpio/gpiolib-acpi.c | 2 +-
drivers/gpio/gpiolib-of.c | 6 +++---
drivers/gpio/gpiolib.c | 16 ++++++++--------
3 files changed, 12 insertions(+), 12 deletions(-)
--
2.40.0.1.gaa8946217a0b
next reply other threads:[~2023-07-03 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 12:18 Andy Shevchenko [this message]
2023-07-03 12:18 ` [PATCH v1 1/3] gpiolib: of: Don't use GPIO chip fwnode in of_gpiochip_*() Andy Shevchenko
2023-07-03 12:18 ` [PATCH v1 2/3] gpiolib: acpi: Don't use GPIO chip fwnode in acpi_gpiochip_find() Andy Shevchenko
2023-07-03 13:15 ` Andy Shevchenko
2023-07-03 12:18 ` [PATCH v1 3/3] gpiolib: Do not alter GPIO chip fwnode member Andy Shevchenko
2023-07-03 14:06 ` [PATCH v1 0/3] gpiolib: Avpid modifying GPIO chip fwnode Benjamin Tissoires
2023-07-03 14:14 ` Andy Shevchenko
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=20230703121838.70898-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=benjamin.tissoires@redhat.com \
--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 \
/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).