From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Konrad Dybcio <konradybcio@kernel.org>,
Bjorn Andersson <andersson@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
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Rob Clark <robin.clark@oss.qualcomm.com>
Subject: Re: [PATCH] arm64: dts: qcom: Remove sdm845-cheza boards
Date: Tue, 15 Jul 2025 17:45:55 +0200 [thread overview]
Message-ID: <b0e229db-0fc5-46e0-a6d9-876ba77a8b0f@kernel.org> (raw)
In-Reply-To: <6220dea5-32e6-4ee3-ae83-96405362783e@oss.qualcomm.com>
On 15/07/2025 16:28, Konrad Dybcio wrote:
>>>
>>> Link: https://lore.kernel.org/linux-arm-msm/5567e441-055d-443a-b117-ec16b53dc059@oss.qualcomm.com/
>>> Signed-off-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
>>> ---
>>> arch/arm64/boot/dts/qcom/Makefile | 3 -
>>> arch/arm64/boot/dts/qcom/sdm845-cheza-r1.dts | 238 -----
>>> arch/arm64/boot/dts/qcom/sdm845-cheza-r2.dts | 238 -----
>>> arch/arm64/boot/dts/qcom/sdm845-cheza-r3.dts | 174 ----
>>> arch/arm64/boot/dts/qcom/sdm845-cheza.dtsi | 1330 --------------------------
>>> 5 files changed, 1983 deletions(-)
>>
>> What about compatible bindings? If this is the last user, it should be
>> dropped as well (second patch).
>
> My understanding was that bindings are generally good to stay..
Is there another user, like other projects? If not, we don't need them.
There is no benefit in documenting something if no one uses it.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-07-15 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 13:26 [PATCH] arm64: dts: qcom: Remove sdm845-cheza boards Konrad Dybcio
2025-07-15 13:45 ` Krzysztof Kozlowski
2025-07-15 14:28 ` Konrad Dybcio
2025-07-15 15:45 ` Krzysztof Kozlowski [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=b0e229db-0fc5-46e0-a6d9-876ba77a8b0f@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.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=marijn.suijten@somainline.org \
--cc=robh@kernel.org \
--cc=robin.clark@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;
as well as URLs for NNTP newsgroup(s).