Thread (15 messages) 15 messages, 9 authors, 2025-09-02

Re: [PATCH 00/21] gpiolib: fence off legacy interfaces

From: Bartosz Golaszewski <hidden>
Date: 2025-08-11 13:10:37
Also in: linux-gpio, linux-input, linux-leds, linux-m68k, linux-media, linux-mips, linux-samsung-soc, linux-sh, linux-sound, linux-usb, linux-wireless, lkml, platform-driver-x86

On Fri, 8 Aug 2025 17:17:44 +0200, Arnd Bergmann [off-list ref] said:
From: Arnd Bergmann <arnd@arndb.de>

Commit 678bae2eaa81 ("gpiolib: make legacy interfaces optional") was
merged for linux-6.17, so now it is possible to use the legacy interfaces
conditionally and eventually have the support left out of the kernel
whenever it is not needed.

I created six patches to force-enable CONFIG_GPIOLIB_LEGACY on the
few (mostly ancient) platforms that still require this, plus a set of
patches to either add the corresponding Kconfig dependencies that make
the device drivers conditional on that symbol, or change them to no
longer require it.

The final patch ends up turning the Kconfig symbol off by default,
which of course depends on everything else getting merged first to avoid
build errors.

I would suggest that patches 1-20 can just get merged through the
respective maintainer trees independently when they are deemed ready,
and the final patch can wait another merge window.
Oh, not at all, I'm fine sending a second PR late into the merge window to
get that done in a single cycle.

Thanks for doing this, awesome work!

Bartosz
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help