From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.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
Subject: Re: [PATCH 1/3] arm64: dts: qcom: rename qcs8300 to monaco
Date: Wed, 24 Sep 2025 12:10:11 +0200 [thread overview]
Message-ID: <b17e95af-0fd4-450a-85ce-5e3ba1e9891b@oss.qualcomm.com> (raw)
In-Reply-To: <20250923-rename-dts-v1-1-21888b68c781@oss.qualcomm.com>
On 9/23/25 1:01 PM, Dmitry Baryshkov wrote:
> The QCS8300 and QCS8275 are two variants of the same die with no
> difference visible to the Linux kernel, which are collectively named as
> 'monaco'. Rather than trying to using the name, which is not always
> relevant, follow the example of 'lemans' and rename qcs8300.dtsi to
> monaco.dtsi (and qcs8300-pmics.dtsi to monaco-pmics.dtsi).
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2025-09-24 10:10 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 [this message]
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
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=b17e95af-0fd4-450a-85ce-5e3ba1e9891b@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=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