linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tengfei Fan <quic_tengfan@quicinc.com>,
	andersson@kernel.org, konrad.dybcio@linaro.org,
	linus.walleij@linaro.org, robh@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	dmitry.baryshkov@linaro.org
Cc: linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@quicinc.com
Subject: Re: [PATCH v3 1/2] dt-bindings: pinctrl: qcom: update compatible name for match with driver
Date: Wed, 13 Mar 2024 08:23:05 +0100	[thread overview]
Message-ID: <60a0e51f-dc0e-4bbf-8127-f987ac2aae71@linaro.org> (raw)
In-Reply-To: <ef237b3c-8613-4cd8-9391-e4a08d50cc6c@quicinc.com>

On 13/03/2024 02:30, Tengfei Fan wrote:
> 
> 
> On 3/12/2024 6:55 PM, Krzysztof Kozlowski wrote:
>> On 12/03/2024 08:47, Tengfei Fan wrote:
>>>
>>>
>>> On 3/12/2024 3:41 PM, Krzysztof Kozlowski wrote:
>>>> On 12/03/2024 03:58, Tengfei Fan wrote:
>>>>> Use compatible name "qcom,sm4450-tlmm" instead of "qcom,sm4450-pinctrl"
>>>>> to match the compatible name in sm4450 pinctrl driver.
>>>>>
>>>>> Fixes: 7bf8b78f86db ("dt-bindings: pinctrl: qcom: Add SM4450 pinctrl")
>>>>> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>>>> Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
>>>>> ---
>>>>>    Documentation/devicetree/bindings/pinctrl/qcom,sm4450-tlmm.yaml | 2 +-
>>>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> Wasn't this applied?
>>>
>>> My test code base on tag: next-20240308, this patch is still not applied.
>>>
>>> In fact, the following dt binding check warning only can be got before
>>> this patch is applied.
>>>
>>
>> Please read all emails in the previous thread. You ignored two emails in
>> the past and apparently one more recent.
> 
> I don't know if you mean I ignored the email which related with "Patch 
> applied" tag from Linus Walleij. If so, the following is the reasion why 
> I still include this patch:

Yep, that's the one. Please do not send patches which were already
applied. It causes unnecessary effort on reviewer and maintainer side.

> 
> I synced the latest upstream code on 03/12/2024, the latest tag is 
> next-20240308, this tag still doesn't include this patch[PATCH v3 1/2].

Happens, considering Linus applied it after 8th of March, I think.

> 
> Dt binding check still get warning if I only send [PATCH v3 2/2] patch 
> to upstream base on next-20240308. so I include this patch[PATCH v3 1/2] 

If you send patch 1+2, dt_binding_check will have exactly the same
result. I don't know about what sort of dt binding check you talk, but
for all cases: you changed nothing by sending these two patches in that
regard. Only noise on the lists.

> in patch series even if this patch have "Patch applied" tag.
> 
> Looking forward to getting your advice if submitting patch series this 
> way is problematic.

Do not send patches which are known to be applied.

Best regards,
Krzysztof


  reply	other threads:[~2024-03-13  7:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12  2:58 [PATCH v3 0/2] update SM4450 pinctrl document Tengfei Fan
2024-03-12  2:58 ` [PATCH v3 1/2] dt-bindings: pinctrl: qcom: update compatible name for match with driver Tengfei Fan
2024-03-12  7:41   ` Krzysztof Kozlowski
2024-03-12  7:47     ` Tengfei Fan
2024-03-12 10:55       ` Krzysztof Kozlowski
2024-03-13  1:30         ` Tengfei Fan
2024-03-13  7:23           ` Krzysztof Kozlowski [this message]
2024-03-13  7:55             ` Tengfei Fan
2024-03-13  9:11               ` Krzysztof Kozlowski
2024-03-13 10:31                 ` Tengfei Fan
2024-03-12  2:58 ` [PATCH v3 2/2] dt-bindings: pinctrl: qcom: update functions to " Tengfei Fan
2024-03-13 16:52   ` Krzysztof Kozlowski
2024-03-28  8:57   ` 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=60a0e51f-dc0e-4bbf-8127-f987ac2aae71@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=kernel@quicinc.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@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=quic_tengfan@quicinc.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;
as well as URLs for NNTP newsgroup(s).