devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
	William Zhang <william.zhang@broadcom.com>,
	linux-arm-kernel@lists.infradead.org
Cc: Kursad Oney <kursad.oney@broadcom.com>,
	Joel Peshkin <joel.peshkin@broadcom.com>,
	Anand Gore <anand.gore@broadcom.com>,
	Dan Beygelman <dan.beygelman@broadcom.com>,
	Florian Fainelli <florian.fainelli@broadcom.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: arm: add bcmbca device tree binding document
Date: Fri, 22 Apr 2022 14:17:51 -0700	[thread overview]
Message-ID: <20220422211751.2029442-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20220413192645.7067-2-william.zhang@broadcom.com>

On Wed, 13 Apr 2022 12:26:41 -0700, William Zhang <william.zhang@broadcom.com> wrote:
> Add arch bcmbca device tree binding document for Broadcom ARM based
> broadband SoC chipsets. In this change, only BCM47622 is added. Other
> chipsets will be added in the future.
> 
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> ---

Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
--
Florian

  parent reply	other threads:[~2022-04-22 22:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-13 19:26 [PATCH v2 0/5] arm: bcmbca: introduce the bcmbca architecture and 47622 SOC William Zhang
2022-04-13 19:26 ` [PATCH v2 1/5] dt-bindings: arm: add bcmbca device tree binding document William Zhang
2022-04-14  7:29   ` Krzysztof Kozlowski
2022-04-14 17:38     ` William Zhang
2022-04-17 18:13       ` Krzysztof Kozlowski
2022-04-19 19:29         ` William Zhang
2022-04-17 18:14   ` Krzysztof Kozlowski
2022-04-22 21:17   ` Florian Fainelli [this message]
2022-04-13 19:26 ` [PATCH v2 3/5] ARM: dts: add dts files for bcmbca soc 47622 William Zhang
2022-04-22 21:18   ` 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=20220422211751.2029442-1-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --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=krzk+dt@kernel.org \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --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).