From: Florian Fainelli <f.fainelli@gmail.com>
To: William Zhang <william.zhang@broadcom.com>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>
Cc: anand.gore@broadcom.com, dan.beygelman@broadcom.com,
joel.peshkin@broadcom.com, tomer.yacoby@broadcom.com,
kursad.oney@broadcom.com, samyon.furman@broadcom.com,
philippe.reynes@softathome.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 v3 0/3] arm: bcmbca: add bcm6846 SoC support
Date: Wed, 8 Jun 2022 11:19:50 +0200 [thread overview]
Message-ID: <96408912-aaa3-ba55-cdfb-3e316ae6e324@gmail.com> (raw)
In-Reply-To: <20220601022215.32494-1-william.zhang@broadcom.com>
On 6/1/2022 4:22 AM, William Zhang wrote:
> This change adds the basic support for Broadcom's ARMv7 based
> Broadband SoC BCM6846. The initial support includes a bare-bone dts
> for dual core ARM A7 with a Broadcom uart.
>
> Changes in v3:
> - Simplify dt-bindings patch subject line
> - Fix timer PPI interrupt cpu mask for dual core cpu
> - Remove unnecessary cpu_on and cpu_off properties from psci node
> - Add the missing gic registers and interrupts property to gic node
>
> Changes in v2:
> - Add new line between entries
Series applied, thanks William! I will comment on the VFP fixup separately.
--
Florian
prev parent reply other threads:[~2022-06-08 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 2:22 [PATCH v3 0/3] arm: bcmbca: add bcm6846 SoC support William Zhang
2022-06-01 2:22 ` [PATCH v3 1/3] dt-bindings: arm: add BCM6846 SoC William Zhang
2022-06-01 2:22 ` [PATCH v3 2/3] ARM: dts: add dts files for bcmbca SoC bcm6846 William Zhang
2022-06-08 9:19 ` 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=96408912-aaa3-ba55-cdfb-3e316ae6e324@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=philippe.reynes@softathome.com \
--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).