From: Shawn Guo <shengchao.guo@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Deepti Jaggi <deepti.jaggi@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: arm: cpus: Add compatible qcom,oryon-1-5
Date: Tue, 14 Apr 2026 09:21:52 +0800 [thread overview]
Message-ID: <ad2WsFuUjtcjZ1wU@QCOM-aGQu4IUr3Y> (raw)
In-Reply-To: <d671229f-1c9f-470f-b1d1-7d015c0721e8@kernel.org>
On Mon, Apr 13, 2026 at 06:08:49PM +0200, Krzysztof Kozlowski wrote:
> On 13/04/2026 16:34, Shawn Guo wrote:
> > In short, there will be Nord DTS using the binding coming, and I do not
>
> Maybe there will, maybe there will not.
>
> > think posting them at the same time should be a requirement.
>
> Well, it is a requirement as I explained previously, said that
> *multiple* times on the mailing list, documented expectations in
> mentioned/linked email threads.
To be honest, I can only read the following from mentioned email
threads.
- Binding and DTS should be organized in separate series per subsystem
- DTS should reference binding series by a lore link
These are what I'm trying to do, and I'm not just posting DTS
simultaneously. I do not really read the requirement of posting
binding and DTS using it simultaneously from the email threads.
Taking a step back, even if the requirement is mentioned in an email
thread like this one, I'm not sure it's the correct or well received
way to define a requirement. And that might be why you had to keep
repeating yourself.
> It's also documented in submitting
> patches in DT (although not with that strong wording).
Either I'm blind or reading the wrong document. I failed to find
the requirement of posting binding and DTS using it simultaneously
in Documentation/devicetree/bindings/submitting-patches.rst. Could you
point it out explicitly?
Shawn
next prev parent reply other threads:[~2026-04-14 1:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 9:16 [PATCH 0/2] dt-bindings: arm: cpus: Fix and extend Qualcomm Oryon compatibles Shawn Guo
2026-04-13 9:16 ` [PATCH 1/2] dt-bindings: arm: cpus: Restore qcom,oryon-1-4 compatible Shawn Guo
2026-04-13 9:57 ` Konrad Dybcio
2026-04-13 10:01 ` Krzysztof Kozlowski
2026-04-13 12:06 ` Shawn Guo
2026-04-13 9:16 ` [PATCH 2/2] dt-bindings: arm: cpus: Add compatible qcom,oryon-1-5 Shawn Guo
2026-04-13 9:58 ` Konrad Dybcio
2026-04-13 10:02 ` Krzysztof Kozlowski
2026-04-13 12:36 ` Shawn Guo
2026-04-13 12:40 ` Krzysztof Kozlowski
2026-04-13 13:10 ` Shawn Guo
2026-04-13 13:30 ` Krzysztof Kozlowski
2026-04-13 14:34 ` Shawn Guo
2026-04-13 16:08 ` Krzysztof Kozlowski
2026-04-14 1:21 ` Shawn Guo [this message]
2026-04-14 6:23 ` Krzysztof Kozlowski
2026-04-14 6:59 ` Shawn Guo
2026-04-14 7:05 ` Krzysztof Kozlowski
2026-04-14 7:11 ` Krzysztof Kozlowski
2026-04-14 8:01 ` Shawn Guo
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=ad2WsFuUjtcjZ1wU@QCOM-aGQu4IUr3Y \
--to=shengchao.guo@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=deepti.jaggi@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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