mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Joe Perches <joe@perches.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 12:00:52 -0700	[thread overview]
Message-ID: <db4b9db9-fa02-4b92-3b9a-bd866fa0e73e@gmail.com> (raw)
In-Reply-To: <04eb301f5b3adbefdd78e76657eff0acb3e3d87f.camel@perches.com>



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.
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
>   MAINTAINERS | 64 ++++++++++++++++++++++++++++++-------------------------------
>   1 file changed, 32 insertions(+), 32 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 47d9862b21a95..0278782c14e19 100644
> --- 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:.
-- 
Florian

  reply	other threads:[~2022-04-19 19:01 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 [this message]
2022-04-19 23:11   ` Joe Perches
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=db4b9db9-fa02-4b92-3b9a-bd866fa0e73e@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=joe@perches.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®