From: Krzysztof Kozlowski <krzk@kernel.org>
To: Xilin Wu <sophon@radxa.com>,
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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>,
Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>,
Ram Kumar Dwivedi <quic_rdwivedi@quicinc.com>
Subject: Re: [PATCH RFC 0/2] arm64: dts: qcom: qcs6490: Introduce Radxa Dragon Q6A
Date: Fri, 12 Sep 2025 10:12:54 +0200 [thread overview]
Message-ID: <1ae48740-1788-4304-be86-455251a02ce3@kernel.org> (raw)
In-Reply-To: <20250912-radxa-dragon-q6a-v1-0-8ccdbf9cd19b@radxa.com>
On 12/09/2025 10:03, Xilin Wu wrote:
> base-commit: 51095600e8c19d53729a7fbd273abc4435a25e9b
> change-id: 20250912-radxa-dragon-q6a-eedcdeaf3e66
> prerequisite-message-id: <20250902164900.21685-1-quic_rdwivedi@quicinc.com>
> prerequisite-patch-id: 257564b609217fda19c9f3424fcd9f6e2ce3ef3c
> prerequisite-patch-id: a8f21781f3bff140260100b74041752000c06000
> prerequisite-patch-id: b46127e2433ede17cc5e1a012f58041c6ef97b13
> prerequisite-patch-id: e8978c5a30373c3ff312b2c8720f586c389f18f8
> prerequisite-message-id: <20250911043256.3523057-1-viken.dadhaniya@oss.qualcomm.com>
> prerequisite-patch-id: c7a057030b78afbbb231280de3765294c006c6f8
> prerequisite-patch-id: 56011305aa35e4c64fc7d63950764807cb81cc4d
> prerequisite-patch-id: c3d3b313ac6abe4ec10fd820b6a9bbc63fdbdb82
> prerequisite-patch-id: 63ee94d0ccd40f60a98b0004d627ad2e7b440d25
> prerequisite-patch-id: 392e8f1902571e5035d5af72e40dc474b5f1b274
> prerequisite-patch-id: e38fba722bdabc02ba09d2dc51df7010dbe28168
> prerequisite-patch-id: a3ca5dba8def5769ffb4b95df2963da60a736f96
> prerequisite-patch-id: 4c0fe8d677d73aaf1b5b842e072246d84729d1c4
So the RFC is because it cannot be yet merged? Please always add such
note in the cover letter.
Also, are you sure these are real dependencies? Like REALLY real
dependencies?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-09-12 8:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 8:03 [PATCH RFC 0/2] arm64: dts: qcom: qcs6490: Introduce Radxa Dragon Q6A Xilin Wu
2025-09-12 8:03 ` [PATCH RFC 1/2] dt-bindings: arm: qcom: Add " Xilin Wu
2025-09-12 8:16 ` Krzysztof Kozlowski
2025-09-12 8:03 ` [PATCH RFC 2/2] arm64: dts: qcom: qcs6490: Introduce " Xilin Wu
2025-09-12 8:15 ` Krzysztof Kozlowski
2025-09-12 9:07 ` Konrad Dybcio
2025-09-12 8:12 ` Krzysztof Kozlowski [this message]
2025-09-12 8:25 ` [PATCH RFC 0/2] " Xilin Wu
2025-09-12 8:53 ` Krzysztof Kozlowski
2025-09-12 8:16 ` Krzysztof Kozlowski
2025-09-12 8:56 ` Konrad Dybcio
2025-09-12 9:04 ` Xilin Wu
2025-09-12 9:15 ` Konrad Dybcio
2026-04-07 10:16 ` Andriy Sharandakov
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=1ae48740-1788-4304-be86-455251a02ce3@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=neil.armstrong@linaro.org \
--cc=quic_rdwivedi@quicinc.com \
--cc=robh@kernel.org \
--cc=sophon@radxa.com \
--cc=viken.dadhaniya@oss.qualcomm.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