From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
linux-gpio@vger.kernel.org
Cc: Hartley Sweeten <hsweeten@visionengravers.com>,
Alexander Sverdlin <alexander.sverdlin@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Bartosz Golaszewski <brgl@bgdev.pl>
Subject: [PATCH v1 0/2] gpiolib:legacy: Kill GPIOF_DIR_* and GPIOF_INIT_*
Date: Wed, 28 Aug 2024 17:23:56 +0300 [thread overview]
Message-ID: <20240828142554.2424189-1-andriy.shevchenko@linux.intel.com> (raw)
Shrink the legacy API and definition surface by killing the (internal)
definitions. This, in particular, will fix a couple of drivers that took
it wrong.
This is assumed to go via BPIOLIB tree as this is quite small series and
most of the changes related to it.
Andy Shevchenko (2):
gpiolib: legacy: Kill GPIOF_INIT_* definitions
gpiolib: legacy: Kill GPIOF_DIR_* definitions
arch/arm/mach-ep93xx/vision_ep9307.c | 6 ++----
arch/mips/bcm63xx/boards/board_bcm963xx.c | 2 +-
drivers/gpio/gpiolib-legacy.c | 5 ++---
include/linux/gpio.h | 12 +++---------
4 files changed, 8 insertions(+), 17 deletions(-)
--
2.43.0.rc1.1336.g36b5255a03ac
next reply other threads:[~2024-08-28 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 14:23 Andy Shevchenko [this message]
2024-08-28 14:23 ` [PATCH v1 1/2] gpiolib: legacy: Kill GPIOF_INIT_* definitions Andy Shevchenko
2024-08-30 22:35 ` Linus Walleij
2024-08-28 14:23 ` [PATCH v1 2/2] gpiolib: legacy: Kill GPIOF_DIR_* definitions Andy Shevchenko
2024-08-30 22:35 ` Linus Walleij
2024-08-28 15:11 ` [PATCH v1 0/2] gpiolib:legacy: Kill GPIOF_DIR_* and GPIOF_INIT_* Andy Shevchenko
2024-08-28 17:05 ` Alexander Sverdlin
2024-09-02 9:47 ` 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=20240828142554.2424189-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=alexander.sverdlin@gmail.com \
--cc=brgl@bgdev.pl \
--cc=hsweeten@visionengravers.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tsbogend@alpha.franken.de \
/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).