From: Johan Hovold <johan@kernel.org>
To: Abel Vesa <abel.vesa@linaro.org>
Cc: 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>,
Sibi Sankar <quic_sibis@quicinc.com>,
Rajendra Nayak <quic_rjendra@quicinc.com>,
Xilin Wu <wuxilin123@gmail.com>,
Jens Glathe <jens.glathe@oldschoolsolutions.biz>,
Srinivas Kandagatla <srini@kernel.org>,
Johan Hovold <johan+linaro@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Konrad Dybcio <quic_kdybcio@quicinc.com>
Subject: Re: [PATCH 0/7] arm64: dts: qcom: x1e80100-*: Drop useless DP3 compatible override
Date: Tue, 29 Apr 2025 11:13:04 +0200 [thread overview]
Message-ID: <aBCYIMdEPrhMzNxi@hovoldconsulting.com> (raw)
In-Reply-To: <aBCWdpk2HXPaJPlH@linaro.org>
On Tue, Apr 29, 2025 at 12:05:58PM +0300, Abel Vesa wrote:
> On 25-04-29 10:57:44, Johan Hovold wrote:
> > On Tue, Apr 29, 2025 at 10:42:28AM +0300, Abel Vesa wrote:
> > > It all started with the support for CRD back when we had different
> > > compatibles for eDP and DP. Meanwhile, that has been sorted out and it
> > > is now figured out at runtime while using only the DP compatible.
> > >
> > > It's almost funny how this got copied over from CRD and spread to all
> > > X Elite platforms.
> > >
> > > TBH, the best reason to drop it ASAP is to make sure this doesn't spread
> > > beyond X Elite to newer platforms.
> > >
> > > Functionally nothing changes.
> > >
> > > Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> > > ---
> > > Abel Vesa (7):
> > > arm64: dts: qcom: x1e-crd: Drop useless DP3 compatible override
> > > arm64: dts: acom: x1e80100-qcp: Drop useless DP3 compatible override
> > > arm64: dts: qcom: x1e80100-t14s: Drop useless DP3 compatible override
> > > arm64: dts: qcom: x1e80100-s15: Drop useless DP3 compatible override
> > > arm64: dts: qcom: x1e80100-hp-x14: Drop useless DP3 compatible override
> > > arm64: dts: qcom: x1e80100: Drop useless DP3 compatible override
> > > arm64: dts: qcom: x1e80100-romulus: Drop useless DP3 compatible override
> >
> > Since this is essentially a clean up perhaps you should have squashed
> > these into one patch.
>
> I was actually thinking that before sending, but then I decided to add
> the Fixes tag to each one. Since it's such a trivial worthless cleanup,
> I wasn't sure if the Fixes tags were worth it either.
Right, since it's not a bug you should probably have skipped the Fixes
tags too.
> I can squash them if the consensus is that it's not backporting.
We should definitely not backport these as they are not fixing any bugs.
Johan
next prev parent reply other threads:[~2025-04-29 9:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 7:42 [PATCH 0/7] arm64: dts: qcom: x1e80100-*: Drop useless DP3 compatible override Abel Vesa
2025-04-29 7:42 ` [PATCH 1/7] arm64: dts: qcom: x1e-crd: " Abel Vesa
2025-04-29 7:42 ` [PATCH 2/7] arm64: dts: acom: x1e80100-qcp: " Abel Vesa
2025-04-29 7:42 ` [PATCH 3/7] arm64: dts: qcom: x1e80100-t14s: " Abel Vesa
2025-04-29 7:42 ` [PATCH 4/7] arm64: dts: qcom: x1e80100-s15: " Abel Vesa
2025-04-29 7:42 ` [PATCH 5/7] arm64: dts: qcom: x1e80100-hp-x14: " Abel Vesa
2025-04-29 7:42 ` [PATCH 6/7] arm64: dts: qcom: x1e80100: " Abel Vesa
2025-04-29 7:42 ` [PATCH 7/7] arm64: dts: qcom: x1e80100-romulus: " Abel Vesa
2025-04-29 8:57 ` [PATCH 0/7] arm64: dts: qcom: x1e80100-*: " Johan Hovold
2025-04-29 9:05 ` Abel Vesa
2025-04-29 9:13 ` Johan Hovold [this message]
2025-04-29 9:20 ` Abel Vesa
2025-04-29 12:11 ` Dmitry Baryshkov
2025-04-29 23:26 ` Sebastian Reichel
2025-04-30 7:37 ` Jens Glathe
2025-04-30 9:39 ` Abel Vesa
2025-04-30 10:35 ` Konrad Dybcio
2025-05-03 5:46 ` Dmitry Baryshkov
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=aBCYIMdEPrhMzNxi@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=johan+linaro@kernel.org \
--cc=konrad.dybcio@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=quic_kdybcio@quicinc.com \
--cc=quic_rjendra@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
--cc=wuxilin123@gmail.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