From: Niklas Cassel <cassel@kernel.org>
To: Rayyan Ansari <rayyan.ansari@linaro.org>
Cc: devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Bjorn Andersson <andersson@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
de Goede <hdegoede@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH 1/3] ARM: dts: qcom: {a,i}pq8064: correct clock-names in sata node
Date: Wed, 17 Jul 2024 15:11:37 +0200 [thread overview]
Message-ID: <ZpfDCStcxnec712U@ryzen.lan> (raw)
In-Reply-To: <D2ROZY3KYF19.3KJC3CS82AWMO@linaro.org>
On Wed, Jul 17, 2024 at 10:05:09AM +0100, Rayyan Ansari wrote:
>
> Hi Niklas,
>
> Yes, this patch does not depend on the following two patches, I just
> thought that sending this as a series would make sense given that
> patches 2-3 would surface this error (as we can run dtbs_check against
> yaml bindings but not text bindings).
Usually, DT maintainers prefer for DT bindings to go via subsystem trees
(in this case libata).
I guess DT maintainers could have picked the whole series, as they do
occasionally, but they seem to want to avoid this as much as possible.
In this case, considering that the DTS change (patch 1/3) is a strict fix,
I think that it should be merged ASAP (target 6.11 instead of 6.12).
We will queue the DT binding changes for 6.12.
When also taking into consideration that the DT bindings and DTS changes
have different trees, splitting the series was probably the right move.
Kind regards,
Niklas
next prev parent reply other threads:[~2024-07-17 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 10:45 [PATCH 0/3] Convert {a,i}pq8064 SATA AHCI controller bindings to dtschema Rayyan Ansari
2024-07-16 10:45 ` [PATCH 1/3] ARM: dts: qcom: {a,i}pq8064: correct clock-names in sata node Rayyan Ansari
2024-07-17 8:45 ` Niklas Cassel
2024-07-17 9:05 ` Rayyan Ansari
2024-07-17 13:11 ` Niklas Cassel [this message]
2024-07-16 10:46 ` [PATCH 2/3] dt-bindings: ata: qcom,ipq806x-ahci: use dtschema Rayyan Ansari
2024-07-16 19:46 ` Krzysztof Kozlowski
2024-07-16 10:46 ` [PATCH 3/3] dt-bindings: ata: qcom,apq8064-ahci: add to dtschema Rayyan Ansari
2024-07-16 19:46 ` Krzysztof Kozlowski
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=ZpfDCStcxnec712U@ryzen.lan \
--to=cassel@kernel.org \
--cc=andersson@kernel.org \
--cc=axboe@kernel.dk \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlemoal@kernel.org \
--cc=hdegoede@redhat.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rayyan.ansari@linaro.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;
as well as URLs for NNTP newsgroup(s).