From: Florian Fainelli <f.fainelli@gmail.com>
To: William Zhang <william.zhang@broadcom.com>,
Linux ARM List <linux-arm-kernel@lists.infradead.org>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>
Cc: kursad.oney@broadcom.com, joel.peshkin@broadcom.com,
tomer.yacoby@broadcom.com, samyon.furman@broadcom.com,
philippe.reynes@softathome.com, anand.gore@broadcom.com,
dan.beygelman@broadcom.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] MAINTAINERS: add bcm63158 to bcmbca arch entry
Date: Wed, 18 May 2022 13:08:21 -0700 [thread overview]
Message-ID: <8337fdf9-6176-5b44-4999-594d41049ca9@gmail.com> (raw)
In-Reply-To: <20220514232800.24653-5-william.zhang@broadcom.com>
On 5/14/2022 4:27 PM, William Zhang wrote:
> Add bcm63158 related files to BCMBCA ARCH maintainer list entry
>
> Signed-off-by: William Zhang <william.zhang@broadcom.com>
> ---
Applied to
https://github.com/Broadcom/stblinux/commits/maintainers/next, thanks!
--
Florian
next prev parent reply other threads:[~2022-05-18 20:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 23:27 [PATCH 0/5] arm64: bcmbca: add bcm63158 soc support William Zhang
2022-05-14 23:27 ` [PATCH 1/5] dt-bindings: arm64: add BCM63158 soc to binding document William Zhang
2022-05-16 16:06 ` Rob Herring
2022-05-16 17:51 ` William Zhang
2022-05-17 14:23 ` Rob Herring
2022-05-18 20:08 ` Florian Fainelli
2022-05-14 23:27 ` [PATCH 2/5] arm64: bcmbca: add arch bcmbca machine entry William Zhang
2022-05-18 20:05 ` Florian Fainelli
2022-05-14 23:27 ` [PATCH 3/5] arm64: dts: add dts files for bcmbca soc 63158 William Zhang
2022-05-18 20:05 ` Florian Fainelli
2022-05-14 23:27 ` [PATCH 4/5] MAINTAINERS: add bcm63158 to bcmbca arch entry William Zhang
2022-05-18 20:08 ` Florian Fainelli [this message]
2022-05-14 23:28 ` [PATCH 5/5] arm64: defconfig: enable bcmbca soc support William Zhang
2022-05-18 20:07 ` 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=8337fdf9-6176-5b44-4999-594d41049ca9@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=joel.peshkin@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philippe.reynes@softathome.com \
--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).