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>,
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 sm6150, x1e80100 and qcs8300
Date: Mon, 27 Oct 2025 17:36:50 -0500 [thread overview]
Message-ID: <176160465180.73268.9117580201716444313.b4-ty@kernel.org> (raw)
In-Reply-To: <20250923-rename-dts-v1-0-21888b68c781@oss.qualcomm.com>
On Tue, 23 Sep 2025 14:01:53 +0300, Dmitry Baryshkov wrote:
> Bjorn said to me that he disliked the conseqeuences of renaming
> qcs615.dtsi to sm6150.dtsi. Let's increase entropy even more and rename
> even more base DTSI files.
>
> Leaving jokes aside. It's not uncommon to see different names for the
> same SoC (or almost same SoC, with no visible differences from the Linux
> side). The platform now known as 'lemans' is a good example, because it
> had been using SA8775P, QCS9100 and QCS9075 in different contexts for
> slightly different modifications. QCS8300 / QCS8275 is another example.
> All such names cause a lot of confusion when somebody tries to follow
> the actual SoC used by the platform.
>
> [...]
Applied, thanks!
[1/3] arm64: dts: qcom: rename qcs8300 to monaco
commit: e50e601ef5b96def44c9ca9685cda6832eb7578e
[2/3] arm64: dts: qcom: rename x1e80100 to hamoa
commit: 8c0b058ab5983a4be6690a76be9b0294853e8e55
[3/3] arm64: dts: qcom: rename sm6150 to talos
commit: 9a5b294dcc21f0b20b586206e5bab9969b4add1c
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-10-27 22:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 11:01 [PATCH 0/3] arm64: dts: qcom: rename dtsi files for sm6150, x1e80100 and qcs8300 Dmitry Baryshkov
2025-09-23 11:01 ` [PATCH 1/3] arm64: dts: qcom: rename qcs8300 to monaco Dmitry Baryshkov
2025-09-24 10:10 ` Konrad Dybcio
2025-09-23 11:01 ` [PATCH 2/3] arm64: dts: qcom: rename x1e80100 to hamoa Dmitry Baryshkov
2025-09-23 11:12 ` Stephan Gerhold
2025-09-23 15:14 ` Dmitry Baryshkov
2025-09-23 18:59 ` Stephan Gerhold
2025-09-23 11:01 ` [PATCH 3/3] arm64: dts: qcom: rename sm6150 to talos Dmitry Baryshkov
2025-09-24 10:10 ` Konrad Dybcio
2025-09-23 13:00 ` [PATCH 0/3] arm64: dts: qcom: rename dtsi files for sm6150, x1e80100 and qcs8300 Luca Weiss
2025-09-23 15:17 ` Dmitry Baryshkov
2025-09-24 10:11 ` Konrad Dybcio
2025-10-27 22:36 ` Bjorn Andersson [this message]
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=176160465180.73268.9117580201716444313.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.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