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>,
	William Zhang <william.zhang@broadcom.com>,
	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: Fri, 22 Apr 2022 10:24:35 -0700	[thread overview]
Message-ID: <b8a5bb60-15d4-0b3b-9d96-758e5136fb46@gmail.com> (raw)
In-Reply-To: <feff60ee8a6d10da7d10b421d18407a5d040680e.camel@perches.com>

On 4/20/22 14:31, Joe Perches wrote:
> On Wed, 2022-04-20 at 11:50 -0700, William Zhang wrote:
>>
>> On 4/19/22 16:11, Joe Perches wrote:
>>> 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.
>>>
>> I can see that we shouldn't use M as maintainer for this Broadcom
>> mailing list email. But I honestly don't understand why we have to use
>> R. Just for the sake of full name?  Not everyone in this distribution
>> list is reviewer.  IMHO I would prefer to change all entries to L
>> without a full name.
> 
> I think "R:" is a better choice than "L:"
> 
> "L:" Mailing list entries have archives that are publicly searchable.
> 
> Are the broadcom bcm-kernel-feedback-list entries publicly archived?

They are not indeed.

> 
> If not, these are one-way entries, so someone sends and hopes only.
> Replies that are sent from these entries are not visible to the public.

OK, fair enough, I will change to:

R: Broadcom internal kernel review list 
<bcm-kernel-feedback-list@broadcom.com>

If that works for everyone?
-- 
Florian

  reply	other threads:[~2022-04-22 17:27 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
2022-04-20 18:50     ` William Zhang
2022-04-20 21:31       ` Joe Perches
2022-04-22 17:24         ` Florian Fainelli [this message]
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=b8a5bb60-15d4-0b3b-9d96-758e5136fb46@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 \
    --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®