From: Marek Vasut <marex@nabladev.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Christoph Niedermaier <cniedermaier@dh-electronics.com>,
devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, kernel@dh-electronics.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: st: stm32mp2xxx: Remove undocumented, unapproved eeprom0wl alias
Date: Tue, 17 Nov 2026 14:41:48 +0100 [thread overview]
Message-ID: <ac1a1214-98dd-48da-b8e1-bc8ef9f09316@nabladev.com> (raw)
In-Reply-To: <20261117133747.244933-2-krzysztof.kozlowski@oss.qualcomm.com>
On 11/17/26 2:37 PM, Krzysztof Kozlowski wrote:
> The eeprom0wl alias was never approved by Devicetree maintainers,
> because it was never documented as actual ABI. There is no in-kernel
> user of it, although there might be U-Boot. External DTS users cannot
> rely on undocumented ABI, thus these are pretty safe to drop.
>
> No new custom aliases are allowed for years now.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> ---
> arch/arm64/boot/dts/st/stm32mp2xxx-dhcos-som.dtsi | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/st/stm32mp2xxx-dhcos-som.dtsi b/arch/arm64/boot/dts/st/stm32mp2xxx-dhcos-som.dtsi
> index bcf63e2ea989..5795b352fccf 100644
> --- a/arch/arm64/boot/dts/st/stm32mp2xxx-dhcos-som.dtsi
> +++ b/arch/arm64/boot/dts/st/stm32mp2xxx-dhcos-som.dtsi
> @@ -10,7 +10,6 @@ aliases {
> serial0 = &usart6;
> serial1 = &uart8;
> eeprom0 = &eeprom0;
> - eeprom0wl = &eeprom0wl;
> rtc0 = &rv3032;
> rtc1 = &rtc;
> };
U-Boot depends on the alias, so please don't drop this one.
next prev parent reply other threads:[~2026-11-17 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 13:37 Krzysztof Kozlowski
2026-11-17 13:41 ` Marek Vasut [this message]
2026-11-17 15:13 ` Krzysztof Kozlowski
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=ac1a1214-98dd-48da-b8e1-bc8ef9f09316@nabladev.com \
--to=marex@nabladev.com \
--cc=alexandre.torgue@foss.st.com \
--cc=cniedermaier@dh-electronics.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@dh-electronics.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--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®