[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <15e1d05f-b7e1-27bc-7363-aefd2d155eea@linaro.org>
Date: Wed, 12 Apr 2023 09:03:31 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Johan Hovold <johan@...nel.org>
Cc: Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.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 08:49, Johan Hovold wrote:
> On Tue, Apr 11, 2023 at 06:58:33PM +0200, Krzysztof Kozlowski wrote:
>> On 11/04/2023 16:23, Johan Hovold wrote:
>>> On Fri, Apr 07, 2023 at 08:07:10PM +0200, Krzysztof Kozlowski wrote:
>>>> Fix typo in drive-strength property name.
>>>
>>> In the future, please try to use the established commit-summary prefix.
>>> In this case:
>>>
>>> arm64: dts: qcom: sc8280xp-x13s:
>>
>> Sure.
>>
>> commit ca1ce7207e53cfe69aee5002eb3795069668da53
>> Author: Johan Hovold <johan+linaro@...nel.org>
>> Date: Fri Aug 5 11:23:17 2022 +0200
>>
>> arm64: dts: qcom: sc8280xp-lenovo-thinkpad-x13s: add alternate touchpad
>
> Yeah, we initially used a longer prefix (including "x13s" which was
> missing in the Subject of this patch), but quite soon decided on using
> the shorter
>
> arm64: dts: qcom: sc8280xp-x13s:
>
> instead.
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
Best regards,
Krzysztof
Powered by blists - more mailing lists