| 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
| ||
|
Message-Id: <175084236984.4074918.12825777412065581866.b4-ty@kernel.org>
Date: Wed, 25 Jun 2025 10:06:09 +0100
From: Lee Jones <lee@...nel.org>
To: Lee Jones <lee@...nel.org>, Pavel Machek <pavel@...nel.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Andrew Davis <afd@...com>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Johan Adolfsson <johan.adolfsson@...s.com>
Cc: linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, kernel@...s.com
Subject: Re: [PATCH v7 0/2] leds-lp50xx: Support reg to set multi_index.
On Tue, 17 Jun 2025 12:23:53 +0200, Johan Adolfsson wrote:
> Since devicetree nodes are (sometimes?) processed in reverse order,
> support reg as the actual multi_index index so yo get well defined
> color order presented in the multi_index file.
> Not sure if reusing reg for this is the correct way or if another
> property such as "multi_index" or similar should be used instead.
> Looks like reg is used for similar things at least.
> Or should the whole "reverse the devicetree" problem be fixed instead?
> Update bindings to match implementation, and add description for the
> reg property.
>
> [...]
Applied, thanks!
[1/2] leds: leds-lp50xx: Handle reg to get correct multi_index
commit: f0022183bfd939f7d3c669cca0bf3aade233c9a5
[2/2] dt-bindings: leds: lp50xx: Document child reg, fix example
commit: d07927c0ca918a6825ef46cb7c012dbc102ac352
--
Lee Jones [李琼斯]
Powered by blists - more mailing lists