From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
cros-qcom-dts-watchers@chromium.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: qcom: rename dtsi files for qcm2290, sc7280 and x1p42100
Date: Sun, 2 Nov 2025 12:09:45 -0600 [thread overview]
Message-ID: <176210698627.937813.1347882402480558851.b4-ty@kernel.org> (raw)
In-Reply-To: <20251030-rename-dts-2-v1-0-80c0b81c4d77@oss.qualcomm.com>
On Thu, 30 Oct 2025 20:20:12 +0200, Dmitry Baryshkov wrote:
> Follow the earlier example and rename several more base DTSI files for
> the platforms where we have (or expect) several SKU ids for a single
> platform.
>
>
Applied, thanks!
[1/3] arm64: dts: qcom: rename qcm2290 to agatti
commit: 021df9dee9cd63eee1cfae1bb2381db11a1a45d7
[2/3] arm64: dts: qcom: rename sc7280 to kodiak
commit: dd6edcd7d3e42b143a2f86e8d30ded62106a8972
[3/3] arm64: dts: qcom: rename x1p42100 to purwa
commit: ef659a5bd91bed7fae2c2a150f8ecca06599ac03
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
next prev parent reply other threads:[~2025-11-02 18:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 18:20 Dmitry Baryshkov
2025-10-30 18:20 ` [PATCH 1/3] arm64: dts: qcom: rename qcm2290 to agatti Dmitry Baryshkov
2025-10-30 21:16 ` Alexey Klimov
2025-10-31 8:56 ` Konrad Dybcio
2025-10-30 18:20 ` [PATCH 2/3] arm64: dts: qcom: rename sc7280 to kodiak Dmitry Baryshkov
2025-10-31 8:57 ` Konrad Dybcio
2025-10-30 18:20 ` [PATCH 3/3] arm64: dts: qcom: rename x1p42100 to purwa Dmitry Baryshkov
2025-10-31 8:57 ` Konrad Dybcio
2025-11-02 18:09 ` Bjorn Andersson [this message]
2025-11-04 13:56 ` [PATCH 0/3] arm64: dts: qcom: rename dtsi files for qcm2290, sc7280 and x1p42100 Alexey Klimov
2025-11-06 20:18 ` Bjorn Andersson
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=176210698627.937813.1347882402480558851.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--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 \
/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
all inboxes | Powered by JetHome®