From: Florian Fainelli <f.fainelli@gmail.com>
To: William Zhang <william.zhang@broadcom.com>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>
Cc: f.fainelli@gmail.com,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
samyon.furman@broadcom.com, tomer.yacoby@broadcom.com,
philippe.reynes@softathome.com, joel.peshkin@broadcom.com,
dan.beygelman@broadcom.com, kursad.oney@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 0/3] arm: bcmbca: Add BCM63146 SoC support
Date: Mon, 13 Jun 2022 14:18:03 -0700 [thread overview]
Message-ID: <9f60a2d5-d3dd-5732-4c2a-4e249e702a72@gmail.com> (raw)
In-Reply-To: <20220608180100.31749-1-william.zhang@broadcom.com>
On 6/8/22 11:00, William Zhang wrote:
> This change adds the basic support for Broadcom's ARM64 based
> Broadband SoC BCM63146. The initial support includes a bare-bone DTS
> for dual core ARM A53 with a ARM PL011 uart. Linux kernel image can be
> build with the ARM64 defconfig
Series applied, thanks William!
--
Florian
prev parent reply other threads:[~2022-06-13 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 18:00 [PATCH 0/3] arm: bcmbca: Add BCM63146 SoC support William Zhang
2022-06-08 18:00 ` [PATCH 1/3] dt-bindings: arm64: Add BCM63146 SoC William Zhang
2022-06-09 14:48 ` Rob Herring
2022-06-13 21:11 ` Florian Fainelli
2022-06-08 18:00 ` [PATCH 2/3] arm64: dts: Add DTS files for bcmbca SoC BCM63146 William Zhang
2022-06-13 21:18 ` Florian Fainelli [this message]
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=9f60a2d5-d3dd-5732-4c2a-4e249e702a72@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=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).