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>,
	Linus Walleij <linus.walleij@linaro.org>,
	Rob Herring <robh+dt@kernel.org>
Cc: andersson@kernel.org, konrad.dybcio@linaro.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	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 v2 1/2] dt-bindings: pinctrl: qcom: update compatible name for match with driver
Date: Mon, 11 Mar 2024 10:58:36 +0100	[thread overview]
Message-ID: <ec81cbb5-30d9-4104-b59d-ae7cd2d90c48@linaro.org> (raw)
In-Reply-To: <2b512404-bc56-41b8-89aa-dcbb23d7b2bd@quicinc.com>

On 11/03/2024 10:43, Tengfei Fan wrote:
>>>>>>
>>>>>> I think you forgot to update the example:
>>>>>>
>>>>>> Documentation/devicetree/bindings/pinctrl/qcom,sm4450-tlmm.example.dtb:
>>>>>> /example-0/pinctrl@f100000: failed to match any schema with
>>>>>> compatible: ['qcom,sm4450-tlmm']
>>>>>
>>>>> Still a warning in linux-next. Please send a fix.
>>>>
>>>> I understand it as applying 1/2 is the fix so I applied it.
>>>
>>> I will check this warning, and I will fix it.
>>
>> Now? We were all waiting for you to respond here without any effect, so
>> finally I asked Linus to take the patch. In the future, be responsible
>> for your patches and comments happening to them. The same if your
>> applied commit causes issues in the next.
> 
> I will speed up the upstream work of the sm4450.
> Before that, I had been focusing on the work of AIM300.

That's not what I was suggested. I don't care if you work on sm4450,
AIM300 or foo4567. It's about your merged commits and submitted patches.


Best regards,
Krzysztof


  reply	other threads:[~2024-03-11  9:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29  9:25 [PATCH v2 0/2] update SM4450 pinctrl document Tengfei Fan
2024-01-29  9:25 ` [PATCH v2 1/2] dt-bindings: pinctrl: qcom: update compatible name for match with driver Tengfei Fan
2024-01-29 11:22   ` Krzysztof Kozlowski
2024-02-27 13:37   ` Rob Herring
2024-03-08 20:10     ` Rob Herring
2024-03-09 23:44       ` Linus Walleij
2024-03-11  2:27         ` Tengfei Fan
2024-03-11  6:48           ` Krzysztof Kozlowski
2024-03-11  9:43             ` Tengfei Fan
2024-03-11  9:58               ` Krzysztof Kozlowski [this message]
2024-03-09 23:44   ` Linus Walleij
2024-01-29  9:25 ` [PATCH v2 2/2] dt-bindings: pinctrl: qcom: consolidate functions to " Tengfei Fan
2024-01-29 11:24   ` Krzysztof Kozlowski
2024-01-31  8:24     ` Tengfei Fan
2024-01-31  8:34       ` Krzysztof Kozlowski
2024-01-31  8:40         ` Tengfei Fan
2024-01-30  4:38   ` Bjorn Andersson
2024-01-31  8:28     ` Tengfei Fan

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=ec81cbb5-30d9-4104-b59d-ae7cd2d90c48@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.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+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).