From: Joe Perches <joe@perches.com>
To: William Zhang <william.zhang@broadcom.com>,
Broadcom Kernel List <bcm-kernel-feedback-list@broadcom.com>
Cc: Samyon Furman <samyon.furman@broadcom.com>,
Joel Peshkin <joel.peshkin@broadcom.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Dan Beygelman <dan.beygelman@broadcom.com>,
Tomer Yacoby <tomer.yacoby@broadcom.com>,
Anand Gore <anand.gore@broadcom.com>,
Kursad Oney <kursad.oney@broadcom.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] MAINTAINERS: update MAINTAINERS file
Date: Tue, 12 Apr 2022 11:40:02 -0700 [thread overview]
Message-ID: <e3cb339e8123ec84392d3050fbd689fcf2255f4a.camel@perches.com> (raw)
In-Reply-To: <51c11778-b252-53b0-8161-9d7928816b55@broadcom.com>
On Tue, 2022-04-12 at 11:37 -0700, William Zhang wrote:
> Hi Joe,
>
> On 4/12/22 09:38, Joe Perches wrote:
> > On Mon, 2022-04-11 at 10:28 -0700, William Zhang wrote:
> > > Add maintainters, SCM tree, files and directories for the new BCMBCA
> >
> > typo of maintainers
> Thanks for catching that.
>
> >
> > > arch. Only add 47622 for this change and will update in the future
> > > when more SoCs are supported.
> > []
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > []
> > > @@ -3740,6 +3740,20 @@ F: drivers/net/dsa/bcm_sf2*
> > > F: include/linux/dsa/brcm.h
> > > F: include/linux/platform_data/b53.h
> > >
> > > +BROADCOM BCMBCA ARM ARCHITECTURE
> > > +M: William Zhang <william.zhang@broadcom.com>
> > > +M: Anand Gore <anand.gore@broadcom.com>
> > > +M: Kursad Oney <kursad.oney@broadcom.com>
> > > +M: bcm-kernel-feedback-list@broadcom.com
> >
> > Unnamed exploders are not maintainers.
> >
> > Maybe:
> >
> > R: Broadcom BCMBCA reviewers <bcm-kernel-feedback-list@broadcom.com>
> Copied from other BCM entry in this file. It is mailing list which does
> not really need an name. And I guess it is better to be put under L as
> other BCM entry does.
I just sent a patch to convert all of these to R:
https://lore.kernel.org/lkml/04eb301f5b3adbefdd78e76657eff0acb3e3d87f.camel@perches.com/T/#u
next prev parent reply other threads:[~2022-04-12 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 17:28 [PATCH 0/5] arm: bcmbca: introduce the bcmbca architecture and 47622 SOC William Zhang
2022-04-11 17:28 ` [PATCH 1/5] dt-bindings: arm: add bcmbca device tree binding document William Zhang
2022-04-12 11:28 ` Krzysztof Kozlowski
2022-04-11 17:28 ` [PATCH 2/5] arm: bcmbca: add arch bcmbca machine entry William Zhang
2022-04-11 17:28 ` [PATCH 3/5] ARM: dts: add dts files for bcmbca soc 47622 William Zhang
2022-04-12 11:27 ` Krzysztof Kozlowski
2022-04-12 15:37 ` William Zhang
2022-04-12 16:27 ` Krzysztof Kozlowski
2022-04-12 18:38 ` William Zhang
2022-04-11 17:28 ` [PATCH 4/5] MAINTAINERS: update MAINTAINERS file William Zhang
2022-04-12 16:38 ` Joe Perches
2022-04-12 18:37 ` William Zhang
2022-04-12 18:40 ` Joe Perches [this message]
2022-04-12 18:42 ` William Zhang
2022-04-11 17:28 ` [PATCH 5/5] ARM: multi_v7_defconfig: enable CONFIG_ARCH_BCMBCA in armv7 defconfig 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=e3cb339e8123ec84392d3050fbd689fcf2255f4a.camel@perches.com \
--to=joe@perches.com \
--cc=anand.gore@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=dan.beygelman@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=joel.peshkin@broadcom.com \
--cc=kursad.oney@broadcom.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®