linux-kernel - Re: [PATCH v5 5/9] gpio: aggregator: add 'name' attribute for custom GPIO line names

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: <CAMRc=MdoMKdqyzGMFDa3aMz3h=vfZ0OtwARxY7FdsPKcBu9HQA@mail.gmail.com>
Date: Thu, 27 Feb 2025 10:50:34 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Koichiro Den <koichiro.den@...onical.com>
Cc: linux-gpio@...r.kernel.org, geert+renesas@...der.be, 
	linus.walleij@...aro.org, maciej.borzecki@...onical.com, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 5/9] gpio: aggregator: add 'name' attribute for custom
 GPIO line names

On Mon, Feb 24, 2025 at 3:32 PM Koichiro Den <koichiro.den@...onical.com> wrote:
>
> Previously, there was no way to assign names to GPIO lines exported
> through the aggregator when the device was created via sysfs.
>
> Allow users to set custom line names via a 'name' attribute and
> expose them using swnode.
>
> Signed-off-by: Koichiro Den <koichiro.den@...onical.com>
> ---

IMO this should be part of the previous commit, there's no reason to
split the configfs implementation. But only change that if there'll be
a v6, otherwise I'll take it as is.

Bart