From: Florian Fainelli <f.fainelli@gmail.com>
To: Anand Gore <anand.gore@broadcom.com>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>
Cc: kursad.oney@broadcom.com, tomer.yacoby@broadcom.com,
samyon.furman@broadcom.com, dan.beygelman@broadcom.com,
William Zhang <william.zhang@broadcom.com>,
joel.peshkin@broadcom.com, Arnd Bergmann <arnd@arndb.de>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Olof Johansson <olof@lixom.net>, Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
soc@kernel.org
Subject: Re: [PATCH v4 0/3] arm: bcmbca: add bcm6878 soc support
Date: Wed, 8 Jun 2022 11:10:47 +0200 [thread overview]
Message-ID: <98f4a12e-bcce-6cad-f976-a4313f9a8000@gmail.com> (raw)
In-Reply-To: <20220602221646.3127512-1-anand.gore@broadcom.com>
On 6/3/2022 12:16 AM, Anand Gore wrote:
>
> The initial support includes a bare-bone dts
> for dual core ARM v7 with a pl011 uart.
>
> Changes in v4:
> - Fixed subject line
>
> Changes in v3:
> - Simplify subject line
>
> Changes in v2:
> - Fix psci, GIC dts entries
> - Remove extra empty lines
>
> Anand Gore (3):
> ARM: dts: add dts files for bcmbca soc 6878
> dt-bindings: arm: add BCM6878 soc
> MAINTAINERS: add bcm6878 to bcmbca arch entry
Series applied, thanks Anand!
--
Florian
prev parent reply other threads:[~2022-06-08 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 22:16 [PATCH v4 0/3] arm: bcmbca: add bcm6878 soc support Anand Gore
2022-06-02 22:16 ` [PATCH v4 1/3] ARM: dts: add dts files for bcmbca soc 6878 Anand Gore
2022-06-02 22:16 ` [PATCH v4 2/3] dt-bindings: arm: add BCM6878 soc Anand Gore
2022-06-06 21:35 ` [PATCH v4 0/3] arm: bcmbca: add bcm6878 soc support Florian Fainelli
2022-06-08 9:10 ` 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=98f4a12e-bcce-6cad-f976-a4313f9a8000@gmail.com \
--to=f.fainelli@gmail.com \
--cc=anand.gore@broadcom.com \
--cc=arnd@arndb.de \
--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=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=samyon.furman@broadcom.com \
--cc=soc@kernel.org \
--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).