[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52d2b67a-5f5b-0c71-a455-f30b0b7afd57@linaro.org>
Date: Thu, 6 Oct 2022 22:21:36 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Stephan Gerhold <stephan@...hold.net>
Cc: Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
Linus Walleij <linus.walleij@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Shawn Guo <shawn.guo@...aro.org>,
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Vinod Koul <vkoul@...nel.org>,
krishna Lanka <quic_vamslank@...cinc.com>,
Iskren Chernev <iskren.chernev@...il.com>,
Martin Botka <martin.botka@...ainline.org>,
linux-arm-msm@...r.kernel.org, linux-gpio@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/34] pinctrl/arm64: qcom: continued - fix Qualcomm TLMM
pinctrl schema warnings (5th set)
On 06/10/2022 17:49, Stephan Gerhold wrote:
>> .../qcom,sm8450-lpass-lpi-pinctrl.yaml | 13 ++--
>> .../bindings/pinctrl/qcom,sm8450-pinctrl.yaml | 22 ++----
>
> Just a random thought since you are already doing minor style cleanups
> here: Some of these files are named incorrectly, e.g. qcom,sm8450-pinctrl.yaml
> actually documents "qcom,sm8450-tlmm". I noticed this while adding
> qcom,msm8909-tlmm but I have to admit that it did not bother me enough
> to actually prepare a patch for this (and now it would just conflict
> with all your patches). :)
>
> No need to change anything here, just thought I'd mention it.
Sure, I can change this as well. Thanks for sharing!
Best regards,
Krzysztof
Powered by blists - more mailing lists