[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <88b393c4-0b65-c451-3e69-c9f60559218d@linaro.org>
Date: Thu, 13 Apr 2023 10:53:49 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Konrad Dybcio <konrad.dybcio@...aro.org>,
Johan Hovold <johan@...nel.org>
Cc: Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sc8280xp-lenovo-thinkpad: correct pin
drive-strength
On 12/04/2023 09:22, Konrad Dybcio wrote:
>>>
>>> Thanks. Do you know if this rule applies to other long-names? I was
>>> usually keeping full name or shortening them by cutting end, but maybe I
>>> should cut the middle?
>>>
>>> sm8250-sony-xperia-edo-pdx206
>>> sm8250-sony-xperia-edo
>>> sm8250-pdx206
> I do sm8250-pdx206 or sm8250-edo for common dtsi changes
>
> Generally anything that contains the SoC name and isn't ambiguous
> works, IMO. And the more concise, the better.
You should have named the files like this...
Best regards,
Krzysztof
Powered by blists - more mailing lists