From: Rob Herring <robh@kernel.org>
To: William Zhang <william.zhang@broadcom.com>
Cc: anand.gore@broadcom.com, dan.beygelman@broadcom.com,
Rob Herring <robh+dt@kernel.org>,
kursad.oney@broadcom.com,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>,
joel.peshkin@broadcom.com, philippe.reynes@softathome.com,
samyon.furman@broadcom.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
florian.fainelli@broadcom.com, tomer.yacoby@broadcom.com
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: add BCM6846 SoC to device tree binding document
Date: Wed, 25 May 2022 20:59:08 -0500 [thread overview]
Message-ID: <20220526015908.GA2898559-robh@kernel.org> (raw)
In-Reply-To: <20220525175124.7524-2-william.zhang@broadcom.com>
On Wed, 25 May 2022 10:51:22 -0700, William Zhang wrote:
> Add BCM6846 SoC device tree description to bcmbca binding document.
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
>
> ---
>
> Changes in v2:
> - Add new line between entries
>
> 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-05-26 1:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 17:51 [PATCH v2 0/3] arm: bcmbca: add bcm6846 SoC support William Zhang
2022-05-25 17:51 ` [PATCH v2 1/3] dt-bindings: arm: add BCM6846 SoC to device tree binding document William Zhang
2022-05-26 1:59 ` Rob Herring [this message]
2022-05-25 17:51 ` [PATCH v2 2/3] ARM: dts: add dts files for bcmbca SoC bcm6846 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=20220526015908.GA2898559-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=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).