[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e6cc8658-fe93-c2c0-603e-093cdafb3cca@rocketmail.com>
Date: Tue, 18 Apr 2023 23:24:50 +0200
From: Jakob Hauser <jahau@...ketmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc: Sebastian Reichel <sre@...nel.org>, Lee Jones <lee@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Beomho Seo <beomho.seo@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
Stephan Gerhold <stephan@...hold.net>,
Raymond Hackley <raymondhackley@...tonmail.com>,
Pavel Machek <pavel@....cz>, Axel Lin <axel.lin@...ics.com>,
ChiYuan Huang <cy_huang@...htek.com>, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
phone-devel@...r.kernel.org, ~postmarketos/upstreaming@...ts.sr.ht
Subject: Re: [PATCH v2 5/9] regulator: rt5033: Change regulator names to
lowercase
Hi Krzysztof,
On 16.04.23 20:32, Krzysztof Kozlowski wrote:
> On 16/04/2023 14:44, Jakob Hauser wrote:
>> Lowercase is preferred for node names.
>
> This will break all existing users. In-tree and out-of-tree. Where is
> the binding update?
In my reply to Rob's comments in v1 I was pointing out that this will
affect an existing driver. There was no reaction.
As far as I can see, there is no in-tree usage yet. Though I can't tell
about out-of-tree usage. Although if there is, adding the rt5033-charger
driver might already causes the need for changes.
Well, to stay on the safe side, I'll drop this patch in v3 and will
change the bindings (patch 9) back to uppercase.
Kind regards,
Jakob
Powered by blists - more mailing lists