[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <116f0087-17d1-652f-23f5-b114e6082273@linaro.org>
Date: Thu, 30 Jun 2022 21:18:51 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Michael Walle <michael@...le.cc>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: UNGLinuxDriver@...rochip.com, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next 4/4] ARM: dts: lan966x: use new
microchip,lan9668-switch compatible
On 30/06/2022 16:02, Michael Walle wrote:
> The old generic microchip,lan966x-switch compatible string was
> deprecated. Use the new one.
>
> Signed-off-by: Michael Walle <michael@...le.cc>
> ---
> arch/arm/boot/dts/lan966x.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/lan966x.dtsi b/arch/arm/boot/dts/lan966x.dtsi
> index 48971d80c82c..da0657c57cdf 100644
> --- a/arch/arm/boot/dts/lan966x.dtsi
> +++ b/arch/arm/boot/dts/lan966x.dtsi
> @@ -85,7 +85,7 @@ soc {
> ranges;
>
> switch: switch@...00000 {
> - compatible = "microchip,lan966x-switch";
> + compatible = "microchip,lan9668-switch";
While technically correct, the change cannot go via independent trees
and may break out-of-tree users of this DTS.
Usually the nicer way is to use two compatibles (the old as fallback).
Anyway, this one is fine with me - up to subarch maintainer.
Best regards,
Krzysztof
Powered by blists - more mailing lists