From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aaron Kling <webgeek1234@gmail.com>
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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/5] dt-bindings: arm: qcom: Add AYN QCS8550 Devices
Date: Mon, 23 Mar 2026 10:00:24 +0100 [thread overview]
Message-ID: <2228bad7-b356-4274-a7b9-9065c9e35e9d@kernel.org> (raw)
In-Reply-To: <CALHNRZ_2tUuiBBuH-QGi8VQbZSVhQg2KGd-dQVJMq+HKiGwpmg@mail.gmail.com>
On 23/03/2026 09:39, Aaron Kling wrote:
> On Mon, Mar 23, 2026 at 2:51 AM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Sun, Mar 22, 2026 at 09:05:18PM -0500, Aaron Kling wrote:
>>> Namely:
>>> * Odin 2
>>> * Odin 2 Mini
>>> * Odin 2 Portal
>>> * Thor
>>>
>>> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
>>> ---
>>> Documentation/devicetree/bindings/arm/qcom.yaml | 9 +++++++++
>>> 1 file changed, 9 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>>> index d054a8f5632d853509b7cd37f07f02473cf6bf71..ee68963c30eae10fd3b3a5e21bda63ab941893fa 100644
>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>> @@ -1075,6 +1075,15 @@ properties:
>>> - const: qcom,qcs8550
>>> - const: qcom,sm8550
>>>
>>> + - items:
>>> + - enum:
>>> + - ayntec,odin2
>>> + - ayntec,odin2mini
>>> + - ayntec,odin2portal
>>> + - ayntec,thor
>>
>> I already commented on vendor prefix patch, that you incorrectly moved
>> it out from this set. This only stalls your patchsets, because none of
>> the trees will have it thus none will pass any checks.
>
> You mean the checks that passed just fine on v2? This is documented in
> the cover letter, which apparently no one ever reads so I wonder why
> we even write them; and listed as a dep, which said checks pick up
> just fine.
Checks will not be fine, imagine this scenario: Bjorn will pick up this
patchset and next will have failures, because there is no vendor prefix
documented in the next.
>
> As I have mentioned multiple times, the vendor patch is separate
And as I answered to you already twice...
> because I have multiple open series that depend on the vendor and
> there's no telling which one will be picked up first.
...no one will pick up vendor prefix thus your goal will not be
achieved. Nothing in vendor prefix patch explains how should take it to
solve it. People do not take random patches, so if you wanted Rob to
take it, you should have been explicit.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-03-23 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 2:05 [PATCH v3 0/5] arm64: dts: qcom: Support AYN QCS8550 Devices Aaron Kling via B4 Relay
2026-03-23 2:05 ` [PATCH v3 1/5] dt-bindings: arm: qcom: Add " Aaron Kling via B4 Relay
2026-03-23 7:51 ` Krzysztof Kozlowski
2026-03-23 8:39 ` Aaron Kling
2026-03-23 9:00 ` Krzysztof Kozlowski [this message]
2026-03-23 9:04 ` Krzysztof Kozlowski
2026-03-23 16:03 ` Aaron Kling
2026-03-23 16:12 ` Krzysztof Kozlowski
2026-03-23 2:05 ` [PATCH v3 2/5] arm64: dts: qcom: Add AYN QCS8550 Common Aaron Kling via B4 Relay
2026-03-23 2:05 ` [PATCH v3 3/5] arm64: dts: qcom: Add AYN Odin 2 Mini Aaron Kling via B4 Relay
2026-03-23 2:05 ` [PATCH v3 4/5] arm64: dts: qcom: Add AYN Odin 2 Portal Aaron Kling via B4 Relay
2026-03-23 2:05 ` [PATCH v3 5/5] arm64: dts: qcom: Add AYN Thor Aaron Kling via B4 Relay
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=2228bad7-b356-4274-a7b9-9065c9e35e9d@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=webgeek1234@gmail.com \
/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