From: Joe Perches <joe@perches.com>
To: Florian Fainelli <f.fainelli@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: bcm-kernel-feedback-list@broadcom.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Broadcom internal lists aren't maintainers
Date: Tue, 19 Apr 2022 16:11:58 -0700 [thread overview]
Message-ID: <b95d9b1058eed13489adba0bccdeb600950eb153.camel@perches.com> (raw)
In-Reply-To: <db4b9db9-fa02-4b92-3b9a-bd866fa0e73e@gmail.com>
On Tue, 2022-04-19 at 12:00 -0700, Florian Fainelli wrote:
> On 4/12/2022 11:34 AM, Joe Perches wrote:
> > Convert the broadcom internal list M: and L: entries to R: as
> > exploder email addresses are neither maintainers nor mailing lists.
> >
> > Reorder the entries as necessary.
[]
> > diff --git a/MAINTAINERS b/MAINTAINERS
[]
> > @@ -3746,7 +3746,7 @@ F: include/linux/platform_data/b53.h
> >
> > BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE
> > M: Nicolas Saenz Julienne <nsaenz@kernel.org>
> > -L: bcm-kernel-feedback-list@broadcom.com
> > +R: Broadcom Kernel Team <bcm-kernel-feedback-list@broadcom.com>
>
> There is not a "Broadcom Kernel Team", the description of R: appears to
> require some kind of full name, hence the choice of L: instead of R:.
If you don't like "Broadcom Kernel Team", perhaps
"Broadcom Kernel Reviewers" might work for you.
I think it doesn't matter much.
next prev parent reply other threads:[~2022-04-19 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 18:34 Joe Perches
2022-04-19 19:00 ` Florian Fainelli
2022-04-19 23:11 ` Joe Perches [this message]
2022-04-20 18:50 ` William Zhang
2022-04-20 21:31 ` Joe Perches
2022-04-22 17:24 ` Florian Fainelli
2022-04-22 17:42 ` William Zhang
2022-04-22 21:00 ` 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=b95d9b1058eed13489adba0bccdeb600950eb153.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®