linux-kernel - Re: [PATCH] MAINTAINERS: Broadcom internal lists aren't maintainers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aa27b58d-af62-1add-1b27-1fb30ce6b8c5@broadcom.com>
Date:   Fri, 22 Apr 2022 10:42:25 -0700
From:   William Zhang <william.zhang@...adcom.com>
To:     Florian Fainelli <f.fainelli@...il.com>,
        Joe Perches <joe@...ches.com>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     bcm-kernel-feedback-list@...adcom.com,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Broadcom internal lists aren't maintainers



On 4/22/22 10:24, Florian Fainelli wrote:
> 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@...nel.org>
>>>>>> -L:    bcm-kernel-feedback-list@...adcom.com
>>>>>> +R:    Broadcom Kernel Team <bcm-kernel-feedback-list@...adcom.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@...adcom.com>
> 
> If that works for everyone?
Sounds good to me.

Download attachment "smime.p7s" of type "application/pkcs7-signature" (4212 bytes)