From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
William Zhang <william.zhang@broadcom.com>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>
Cc: florian.fainelli@broadcom.com, dan.beygelman@broadcom.com,
joel.peshkin@broadcom.com, philippe.reynes@softathome.com,
kursad.oney@broadcom.com, tomer.yacoby@broadcom.com,
samyon.furman@broadcom.com, anand.gore@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: [PATCH 2/3] arm64: dts: add dts files for bcmbca SoC bcm4912
Date: Wed, 8 Jun 2022 01:16:58 -0700 [thread overview]
Message-ID: <20220608081658.1450367-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20220528005654.13809-3-william.zhang@broadcom.com>
On Fri, 27 May 2022 17:56:52 -0700, William Zhang <william.zhang@broadcom.com> wrote:
> Add dts for ARMv8 based broadband SoC BCM4912. bcm4912.dtsi is the
> SoC description dts header and bcm94912.dts is a simple dts file for
> Broadcom BCM94912 Reference board that only enable the UART port.
>
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> ---
Applied to https://github.com/Broadcom/stblinux/commits/devicetree-arm64/next, thanks!
--
Florian
next prev parent reply other threads:[~2022-06-08 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 0:56 [PATCH 0/3] arm64: bcmbca: add bcm4912 SoC support William Zhang
2022-05-28 0:56 ` [PATCH 1/3] dt-bindings: arm64: add bcm4912 SoC to binding document William Zhang
2022-05-29 13:57 ` Krzysztof Kozlowski
2022-06-08 8:16 ` Florian Fainelli
2022-05-28 0:56 ` [PATCH 2/3] arm64: dts: add dts files for bcmbca SoC bcm4912 William Zhang
2022-06-08 8:16 ` Florian Fainelli [this message]
2022-05-28 0:56 ` [PATCH 3/3] MAINTAINERS: add bcm4912 to bcmbca arch entry William Zhang
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=20220608081658.1450367-1-f.fainelli@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=florian.fainelli@broadcom.com \
--cc=joel.peshkin@broadcom.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.reynes@softathome.com \
--cc=robh+dt@kernel.org \
--cc=samyon.furman@broadcom.com \
--cc=tomer.yacoby@broadcom.com \
--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).