linux-kernel - Re: [PATCH] ARM: dts: aspeed: ahe50dc: Update lm25066 regulator name

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] [day] [month] [year] [list]

Message-ID: <afee602b57f95a2d3162a601832d3a087ea5f0d6.camel@codeconstruct.com.au>
Date: Tue, 27 Feb 2024 08:58:52 +1030
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: Rob Herring <robh@...nel.org>, Zev Weiss <zev@...ilderbeest.net>
Cc: Guenter Roeck <linux@...ck-us.net>, Krzysztof Kozlowski
 <krzysztof.kozlowski+dt@...aro.org>, linux-kernel@...r.kernel.org, Joel
 Stanley <joel@....id.au>, Rob Herring <robh+dt@...nel.org>,
 devicetree@...r.kernel.org,  linux-arm-kernel@...ts.infradead.org, Conor
 Dooley <conor+dt@...nel.org>,  linux-aspeed@...ts.ozlabs.org
Subject: Re: [PATCH] ARM: dts: aspeed: ahe50dc: Update lm25066 regulator name

On Mon, 2024-02-26 at 10:54 -0600, Rob Herring wrote:
> On Mon, 26 Feb 2024 01:17:53 -0800, Zev Weiss wrote:
> > A recent change to the lm25066 driver changed the name of its
> > regulator from vout0 to vout; device-tree users of lm25066's regulator
> > functionality (of which ahe50dc is the only one) thus require a
> > corresponding update.
> > 
> > Signed-off-by: Zev Weiss <zev@...ilderbeest.net>
> > Cc: Conor Dooley <conor+dt@...nel.org>
> > Cc: Guenter Roeck <linux@...ck-us.net>
> > ---
> >  arch/arm/boot/dts/aspeed/aspeed-bmc-delta-ahe50dc.dts | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> 
> 
> My bot found new DT warnings on the .dts files added or changed in this
> series.
> 

For what it's worth I've put together a set of patches that resolve
almost all the warnings in the Aspeed DTSIs. My current approach is to
progressively send them out - I'm starting slow so where possible I can
avoid making the same mistake multiple times.

Andrew