From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
bjorn.andersson@linaro.org, linus.walleij@linaro.org
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: pinctrl: update qcom file list to include yaml files
Date: Fri, 1 Jul 2022 10:32:01 +0100 [thread overview]
Message-ID: <a8d688b8-95ac-1c01-222e-65a6c9f83c8a@linaro.org> (raw)
In-Reply-To: <2d63cbf2-8e59-a8db-3faf-747b92d2eb66@linaro.org>
On 01/07/2022 09:28, Krzysztof Kozlowski wrote:
> On 29/06/2022 11:25, Srinivas Kandagatla wrote:
>> Currently Qualcomm pinctrl MAINTAINERS file list does not include yaml
>> files. Include this for correctness.
>>
>> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
>> ---
>> MAINTAINERS | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index c4648e86dc14..71e7725aa574 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -15765,6 +15765,7 @@ M: Bjorn Andersson <bjorn.andersson@linaro.org>
>> L: linux-arm-msm@vger.kernel.org
>> S: Maintained
>> F: Documentation/devicetree/bindings/pinctrl/qcom,*.txt
>> +F: Documentation/devicetree/bindings/pinctrl/qcom,*.yaml
>
> Instead just:
> Documentation/devicetree/bindings/pinctrl/qcom,*
>
Makes more sense, will do that in next spin.
--srini
>> F: drivers/pinctrl/qcom/
>>
>> PIN CONTROLLER - RENESAS
>
>
> Best regards,
> Krzysztof
prev parent reply other threads:[~2022-07-01 9:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 9:25 [PATCH] MAINTAINERS: pinctrl: update qcom file list to include yaml files Srinivas Kandagatla
2022-07-01 8:28 ` Krzysztof Kozlowski
2022-07-01 9:32 ` Srinivas Kandagatla [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8d688b8-95ac-1c01-222e-65a6c9f83c8a@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).