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

Bartosz Golaszewski <[email protected]>
Newsgroups gmane.linux.ports.mips,gmane.linux.ports.arm.kernel,gmane.linux.kernel,gmane.linux.kernel.samsung-soc,gmane.linux.ports.sh.devel,gmane.linux.kernel.input,gmane.linux.leds,gmane.linux.drivers.video-input-infrastructure,gmane.linux.network,gmane.linux.kernel.wireless.general,gmane.linux.drivers.ath10k.devel,gmane.linux.drivers.platform.x86.devel,gmane.linux.usb.general,gmane.linux.sound,gmane.linux.kernel.gpio
Message-ID <CAMRc=MeyW8gtG_hsLWytCpufQRmg3s5QZenxCvP3MNGmaoo2cA@mail.gmail.com> 
On Fri, 8 Aug 2025 17:17:44 +0200, Arnd Bergmann <[email protected]> said:
> From: Arnd Bergmann <[email protected]>
>
> 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.