From: Jingyi Wang <quic_jingyw@quicinc.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Richard Cochran" <richardcochran@gmail.com>,
<quic_tengfan@quicinc.com>, <linux-arm-msm@vger.kernel.org>,
<linux-gpio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<quic_tingweiz@quicinc.com>, <quic_aiquny@quicinc.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 0/2] pinctrl: qcom: Introduce Pinctrl for QCS8300
Date: Mon, 21 Oct 2024 10:32:53 +0800 [thread overview]
Message-ID: <5fa2080a-f59e-405e-ba52-69d7293e2739@quicinc.com> (raw)
In-Reply-To: <f9dace93-f6c7-40c2-a6d2-60ce8043aa72@lunn.ch>
On 10/19/2024 2:08 AM, Andrew Lunn wrote:
> On Fri, Oct 18, 2024 at 11:19:30AM +0800, Jingyi Wang wrote:
>> Introduce Top Level Mode Multiplexer dt-binding and driver for Qualcomm
>> QCS8300 SoC.
>>
>> Signed-off-by: Jingyi Wang <quic_jingyw@quicinc.com>
>
> I'm curious why you are Cc: netdev for a pin controller patch? Did
> ./scripts/get_maintainer.pl say you should?
>
The cc list was generated by the b4 tools.
> Andrew
>
> ---
> pw-bot: cr
Thanks,
Jingyi
next prev parent reply other threads:[~2024-10-21 2:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 3:19 Jingyi Wang
2024-10-18 3:19 ` [PATCH v3 1/2] dt-bindings: pinctrl: describe qcs8300-tlmm Jingyi Wang
2024-10-18 3:19 ` [PATCH v3 2/2] pinctrl: qcom: add the tlmm driver for QCS8300 platforms Jingyi Wang
2024-10-18 18:08 ` [PATCH v3 0/2] pinctrl: qcom: Introduce Pinctrl for QCS8300 Andrew Lunn
2024-10-21 2:32 ` Jingyi Wang [this message]
2024-10-21 4:27 ` Jingyi Wang
2024-10-21 16:04 ` Andrew Lunn
2024-10-22 12:42 ` Linus Walleij
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=5fa2080a-f59e-405e-ba52-69d7293e2739@quicinc.com \
--to=quic_jingyw@quicinc.com \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.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=netdev@vger.kernel.org \
--cc=quic_aiquny@quicinc.com \
--cc=quic_tengfan@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=richardcochran@gmail.com \
--cc=robh@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
all inboxes | Powered by JetHome®