linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: William Zhang <william.zhang@broadcom.com>
Cc: anand.gore@broadcom.com, samyon.furman@broadcom.com,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>,
	f.fainelli@gmail.com, devicetree@vger.kernel.org,
	Linux ARM List <linux-arm-kernel@lists.infradead.org>,
	kursad.oney@broadcom.com, joel.peshkin@broadcom.com,
	linux-kernel@vger.kernel.org, philippe.reynes@softathome.com,
	tomer.yacoby@broadcom.com, dan.beygelman@broadcom.com
Subject: Re: [PATCH 1/3] dt-bindings: arm: Add BCM63148 SoC
Date: Mon, 13 Jun 2022 12:03:18 -0600	[thread overview]
Message-ID: <20220613180318.GA3990308-robh@kernel.org> (raw)
In-Reply-To: <20220610002113.14483-2-william.zhang@broadcom.com>

On Thu, 09 Jun 2022 17:21:11 -0700, William Zhang wrote:
> Add BCM63148 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>

  reply	other threads:[~2022-06-13 19:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10  0:21 [PATCH 0/3] arm: bcmbca: Add BCM63148 SoC support William Zhang
2022-06-10  0:21 ` [PATCH 1/3] dt-bindings: arm: Add BCM63148 SoC William Zhang
2022-06-13 18:03   ` Rob Herring [this message]
2022-06-13 21:37   ` Florian Fainelli
2022-06-10  0:21 ` [PATCH 2/3] ARM: dts: Add DTS files for bcmbca SoC BCM63148 William Zhang
2022-06-13 21:37   ` Florian Fainelli
2022-06-10  0:21 ` [PATCH 3/3] MAINTAINERS: Add BCM63148 to bcmbca arch entry William Zhang
2022-06-13 21:38   ` 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=20220613180318.GA3990308-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).