Re: [PATCH v5 0/6] gpiolib: fence off legacy interfaces

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Mon, Jun 29, 2026 at 03:03:23PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> This is the remainder of the series previously posted as v2
> in [1]. I've changed the version to v5 for all patches to
> not confuse b4 too much, but the patches are mostly unchanged.
> 
> The patch "Input: soc_button_array - select CONFIG_GPIOLIB_LEGACY"
> was not part of the series last time, but the build bots reported
> this as a regression since I had dropped that since v1.
> 
> I hope that all that remains now can just get merged through the
> gpio tree. The gpio-keys patch needs a bit coordination with
> another patch addressing the same issue that is already in
> flight, so I expect that I'll rebase my series once more when
> that is in a stable branch, but the state I have here should
> just work as-is on top of v7.2-rc1.
> 
>      Arnd
> 
> [1] https://lore.kernel.org/all/20260520183815.2510387-1-arnd@kernel.org/
> 
> Arnd Bergmann (6):
>   [v5] sh: select legacy gpiolib interface
>   [v5] x86/olpc: select GPIOLIB_LEGACY
>   [v5] Input: soc_button_array - select CONFIG_GPIOLIB_LEGACY
>   [v5] Input: gpio-keys: make legacy gpiolib optional
>   [v5] leds: gpio: make legacy gpiolib interface optional
>   [v5] gpiolib: turn off legacy interface by default
> 
>  arch/sh/Kconfig                           |  1 +
>  arch/sh/boards/Kconfig                    |  8 ++++
>  arch/sh/boards/mach-highlander/Kconfig    |  1 +
>  arch/sh/boards/mach-rsk/Kconfig           |  3 ++
>  arch/x86/Kconfig                          |  1 +
>  arch/x86/platform/olpc/olpc-xo1-sci.c     |  2 +-
>  drivers/gpio/Kconfig                      |  9 +++-
>  drivers/input/keyboard/gpio_keys.c        |  9 ++--
>  drivers/input/keyboard/gpio_keys_polled.c |  4 +-
>  drivers/input/misc/Kconfig                |  3 ++
>  drivers/input/misc/soc_button_array.c     |  2 +-

Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> # for input

Could this be done as an immutable branch?

Thanks.

-- 
Dmitry