devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: Johan Hovold <johan+linaro@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Andy Gross <agross@kernel.org>,
	Konrad Dybcio <konrad.dybcio@somainline.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sc8280xp: add TCSR node
Date: Mon, 24 Oct 2022 12:31:55 -0400	[thread overview]
Message-ID: <2901a037-7b0c-1cf4-60fb-b3f6966454ad@linaro.org> (raw)
In-Reply-To: <Y1anKh24QaXcsS74@hovoldconsulting.com>

On 24/10/2022 10:54, Johan Hovold wrote:
>>
>>> The binding has been picked up by Lee now so I posted the dts change.
>>> Could have added a lore link though.
>>
>> This also would work and help a lot.
>>
>> It depends in general on the maintainer - for example Greg does not want
>> to deal with individual patches, especially if DTS is just one patch and
>> USB would be 10 of them. Our toolset is not good for picking up 10 out
>> of 11. For all such cases - please provide link to lore.
>>
>> If however there are just two patches - one DTS and one for maintainer -
>> then having them in one patchset should not cause additional effort for
>> the maintainer.
> 
> I'm pretty sure I saw Lee complaining about Bjorn taking also the
> binding update through the qcom tree recently when someone did just
> that. Apparently it was TCSR related too:
> 
> 	https://lore.kernel.org/all/Yzbk%2F6SQdpNQTahV@google.com/
> 
> Heh. That was you. :)

Yep. It was a patchset of 16 patches where one should go to MFD and 15
to Qualcomm SoC.

>  
>> As you can see on the list, majority of patchsets consist of
>> bindings+DTS. Pretty often entire piece - bindings+driver+DTS.
> 
> Yeah, and whatever alternative you go with, someone will get it wrong or
> complain it seems.

:)

Best regards,
Krzysztof


      reply	other threads:[~2022-10-24 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24 12:58 [PATCH] arm64: dts: qcom: sc8280xp: add TCSR node Johan Hovold
2022-10-24 13:34 ` Krzysztof Kozlowski
2022-10-24 13:42   ` Johan Hovold
2022-10-24 14:09     ` Krzysztof Kozlowski
2022-10-24 14:54       ` Johan Hovold
2022-10-24 16:31         ` Krzysztof Kozlowski [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=2901a037-7b0c-1cf4-60fb-b3f6966454ad@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johan+linaro@kernel.org \
    --cc=johan@kernel.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@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).