linux-kernel - Re: [PATCH] MAINTAINERS: Update maintainers for broadcom USB

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: <3d74b5cf-0f50-ac27-aa21-210507f41858@gmail.com>
Date:   Fri, 7 Oct 2022 11:45:04 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>,
        Justin Chen <justinpopo6@...il.com>
Cc:     linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
        vkoul@...nel.org, kishon@...com, linux-phy@...ts.infradead.org,
        f.fainelli@...il.com, alcooperx@...il.com,
        bcm-kernel-feedback-list@...adcom.com, justin.chen@...adcom.com
Subject: Re: [PATCH] MAINTAINERS: Update maintainers for broadcom USB

On 10/7/22 00:26, Greg KH wrote:
> On Fri, Oct 07, 2022 at 12:19:01AM -0700, Justin Chen wrote:
>> On Thu, Oct 6, 2022 at 11:59 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>>>
>>> On Thu, Oct 06, 2022 at 11:46:45PM -0700, Justin Chen wrote:
>>>> On Thu, Oct 6, 2022 at 11:26 PM Greg KH <gregkh@...uxfoundation.org> wrote:
>>>>>
>>>>> On Thu, Oct 06, 2022 at 04:21:09PM -0700, justinpopo6@...il.com wrote:
>>>>>> From: Justin Chen <justinpopo6@...il.com>
>>>>>>
>>>>>> Al Cooper is no longer the downstream maintainer for broadcom USB.
>>>>>> I will be taking his place as downstream and as an additional
>>>>>> upstream maintainer.
>>>>>
>>>>> What do you mean by "downstream" here?
>>>>>
>>>> Downstream as in internal to Broadcom. Apologies for the confusion.
>>>
>>> Ok, but then why are these all gmail.com addresses?  Why not use your
>>> proper work addresses instead so that we can at least validate that the
>>> patches are coming from a broadcom.com domain?
>>>
>> I believe the idea is we can continue to support as maintainers even
>> if we are no longer part of broadcom without having to change emails.
>> I believe Florian should be able to comment more. :)
> 
> So in other words, broadcom email servers do not allow sending patches
> out without mangling the text?  :)

That was definitively the case years ago due to IT using a Microsoft 
Exchange SMTP server and which had us switch to our gmail.com accounts. 
The "continuity" aspect of not having your email change does matter IMHO 
in that we should always be reachable, at expense of not immediately 
disclosing our employer. Other reasons I heard was that people posting 
publicly with a @broadcom.com email grew tired of being asked when they 
would get a working WLAN driver for their card.

Now we supposedly have a special SMTP server that would not mangle the 
patches and also not add the annoying legalese footer at the end telling 
you to destroy the email.

Does it matter though as long as Jonathan Corbet knows about our 
employer at the time for his lwn.net stats :)?
--
Florian