From: Rob Herring <robh@kernel.org>
To: William Zhang <william.zhang@broadcom.com>
Cc: Linux ARM List <linux-arm-kernel@lists.infradead.org>,
tomer.yacoby@broadcom.com, dan.beygelman@broadcom.com,
kursad.oney@broadcom.com, Rob Herring <robh+dt@kernel.org>,
anand.gore@broadcom.com,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
philippe.reynes@softathome.com, joel.peshkin@broadcom.com,
f.fainelli@gmail.com,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
linux-kernel@vger.kernel.org, samyon.furman@broadcom.com,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: arm64: Add BCM6856 SoC
Date: Thu, 9 Jun 2022 08:50:27 -0600 [thread overview]
Message-ID: <20220609145027.GA3774978-robh@kernel.org> (raw)
In-Reply-To: <20220608180437.31971-2-william.zhang@broadcom.com>
On Wed, 08 Jun 2022 11:04:35 -0700, William Zhang wrote:
> Add BCM6856 SoC device tree description to bcmbca binding document.
>
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> ---
>
> Documentation/devicetree/bindings/arm/bcm/brcm,bcmbca.yaml | 7 +++++++
> 1 file changed, 7 insertions(+)
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-06-09 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 18:04 [PATCH 0/3] arm: bcmbca: Add BCM6856 SoC support William Zhang
2022-06-08 18:04 ` [PATCH 1/3] dt-bindings: arm64: Add BCM6856 SoC William Zhang
2022-06-09 14:50 ` Rob Herring [this message]
2022-06-13 21:18 ` Florian Fainelli
2022-06-08 18:04 ` [PATCH 2/3] arm64: dts: Add DTS files for bcmbca SoC BCM6856 William Zhang
2022-06-13 21:28 ` [PATCH 0/3] arm: bcmbca: Add BCM6856 SoC support Florian Fainelli
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=20220609145027.GA3774978-robh@kernel.org \
--to=robh@kernel.org \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.beygelman@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.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).