[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <900ac3ed-a77c-3cc0-f5ab-c45267a1a4ba@gmail.com>
Date: Tue, 12 Jul 2022 08:36:53 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
William Zhang <william.zhang@...adcom.com>,
Linux ARM List <linux-arm-kernel@...ts.infradead.org>,
Rafał Miłecki <rafal@...ecki.pl>
Cc: kursad.oney@...adcom.com, anand.gore@...adcom.com,
dan.beygelman@...adcom.com, f.fainelli@...il.com,
Broadcom Kernel List <bcm-kernel-feedback-list@...adcom.com>,
joel.peshkin@...adcom.com,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 3/3] arm64: dts: bcmbca: update bcm4808 board dts file
On 7/12/22 00:47, Krzysztof Kozlowski wrote:
> On 12/07/2022 04:11, William Zhang wrote:
>> Update compatible string based on the new bcmbca binding rule
>> for BCM4908 famliy based boards
>
> Typo - family
>
> Please explain why breaking the ABI (and users of these DTS_ is acceptable.
This will be largely targeted towards Rafal who supports these kinds of
devices with an upstream kernel. My understanding is that this is OK
because we will always ship a DTB matching the Linux kernel, and I
believe this is true for both the way that William and his group support
these devices, as well as how OpenWrt, buildroot or other build systems
envision to support these devices.
Rafal, does that sound about right?
--
Florian
Powered by blists - more mailing lists