From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PATCH v1 0/2] gpio: More cleanups to legacy header
Date: Sat, 31 May 2025 22:55:42 +0300 [thread overview]
Message-ID: <20250531195801.3632110-1-andriy.shevchenko@linux.intel.com> (raw)
If I'm not missing anything the 'struct gpio' is not used and
GPIO_DYNAMIC_* constants nowadays are private to gpiolib.c.
Hence this series.
Note, this seems already the case for the upcoming v6.16 cycle, hence
I would like to route these patches as fixes to it to prevent any possible
use of the mentioned definitions in a new code.
Andy Shevchenko (2):
gpio: Remove unused 'struct gpio' definition
gpiolib: Move GPIO_DYNAMIC_* constants to its only user
drivers/gpio/gpiolib.c | 13 +++++++++++++
include/linux/gpio.h | 25 -------------------------
2 files changed, 13 insertions(+), 25 deletions(-)
--
2.47.2
next reply other threads:[~2025-05-31 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-31 19:55 Andy Shevchenko [this message]
2025-05-31 19:55 ` [PATCH v1 1/2] gpio: Remove unused 'struct gpio' definition Andy Shevchenko
2025-06-05 13:31 ` Linus Walleij
2025-05-31 19:55 ` [PATCH v1 2/2] gpiolib: Move GPIO_DYNAMIC_* constants to its only user Andy Shevchenko
2025-06-05 13:32 ` Linus Walleij
2025-06-10 8:11 ` [PATCH v1 0/2] gpio: More cleanups to legacy header Bartosz Golaszewski
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=20250531195801.3632110-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--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
all inboxes | Powered by JetHome®