linux-kernel - Re: [PATCH 10/21] leds: gpio: make legacy gpiolib interface optional

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACRpkdZS1uOMsT3h-kyNQVrVW0R+1mmmOB=EAmqcHQSpo4qAYQ@mail.gmail.com>
Date: Mon, 18 Aug 2025 17:37:08 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Arnd Bergmann <arnd@...nel.org>
Cc: Bartosz Golaszewski <brgl@...ev.pl>, linux-gpio@...r.kernel.org, Lee Jones <lee@...nel.org>, 
	Pavel Machek <pavel@...nel.org>, Arnd Bergmann <arnd@...db.de>, 
	Javier Carrasco <javier.carrasco.cruz@...il.com>, 
	"Gustavo A. R. Silva" <gustavoars@...nel.org>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>, 
	Kees Cook <kees@...nel.org>, Anish Kumar <yesanishhere@...il.com>, 
	Mukesh Ojha <quic_mojha@...cinc.com>, Thomas Zimmermann <tzimmermann@...e.de>, 
	Dmitry Rokosov <ddrokosov@...utedevices.com>, linux-leds@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/21] leds: gpio: make legacy gpiolib interface optional

On Fri, Aug 8, 2025 at 5:22 PM Arnd Bergmann <arnd@...nel.org> wrote:

> From: Arnd Bergmann <arnd@...db.de>
>
> There are still a handful of ancient mips/armv5/sh boards that use the
> gpio_led:gpio member to pass an old-style gpio number, but all modern
> users have been converted to gpio descriptors.
>
> Make the code that deals with this optional so the legacy interfaces
> can be left out for all normal builds.
>
> Signed-off-by: Arnd Bergmann <arnd@...db.de>

I like this, it cleans up things for current systems so they do not need
to carry around so much legacy.

Reviewed-by: Linus Walleij <linus.walleij@...aro.org>

Yours,
Linus Walleij