From: Florian Fainelli <f.fainelli@gmail.com>
To: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
"William Zhang" <william.zhang@broadcom.com>,
"Linux ARM List" <linux-arm-kernel@lists.infradead.org>,
"Rafał Miłecki" <rafal@milecki.pl>
Cc: kursad.oney@broadcom.com, anand.gore@broadcom.com,
dan.beygelman@broadcom.com, f.fainelli@gmail.com,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
joel.peshkin@broadcom.com,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 3/3] arm64: dts: bcmbca: update bcm4808 board dts file
Date: Tue, 12 Jul 2022 08:36:53 -0700 [thread overview]
Message-ID: <900ac3ed-a77c-3cc0-f5ab-c45267a1a4ba@gmail.com> (raw)
In-Reply-To: <d93e55fa-3359-2609-aad5-c80eca78f380@linaro.org>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-12 15:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 2:11 [RFC PATCH 0/3] arm: bcmbca: Update BCM4908 dts for BCMBCA merge William Zhang
2022-07-12 2:11 ` [RFC PATCH 1/3] dt-bindings: arm64: bcmbca: Merge BCM4908 into BCMBCA William Zhang
2022-07-12 7:45 ` Krzysztof Kozlowski
2022-07-12 17:37 ` William Zhang
2022-07-12 18:18 ` Krzysztof Kozlowski
2022-07-13 0:57 ` William Zhang
2022-07-13 10:50 ` Rafał Miłecki
2022-07-13 10:58 ` Rafał Miłecki
2022-07-13 18:37 ` William Zhang
2022-07-13 20:23 ` Rafał Miłecki
2022-07-13 20:29 ` William Zhang
2022-07-18 20:02 ` Rob Herring
2022-07-18 22:59 ` William Zhang
2022-07-13 16:21 ` Florian Fainelli
2022-07-12 2:11 ` [RFC PATCH 2/3] dt-bindings: arm64: bcm4908: remove binding document William Zhang
2022-07-12 7:46 ` Krzysztof Kozlowski
2022-07-12 2:11 ` [RFC PATCH 3/3] arm64: dts: bcmbca: update bcm4808 board dts file William Zhang
2022-07-12 7:47 ` Krzysztof Kozlowski
2022-07-12 15:36 ` Florian Fainelli [this message]
2022-07-12 15:50 ` Krzysztof Kozlowski
2022-07-12 17:48 ` William Zhang
2022-07-12 18:20 ` Krzysztof Kozlowski
2022-07-13 0:59 ` William Zhang
2022-07-13 10:55 ` Rafał Miłecki
2022-07-13 11:09 ` Krzysztof Kozlowski
2022-07-13 12:00 ` Rafał Miłecki
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=900ac3ed-a77c-3cc0-f5ab-c45267a1a4ba@gmail.com \
--to=f.fainelli@gmail.com \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.beygelman@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=joel.peshkin@broadcom.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
--cc=william.zhang@broadcom.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).