Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Fri, 7 Oct 2022 21:22:07 +0200
From:   Greg KH <gregkh@linuxfoundation.org>
To:     Florian Fainelli <f.fainelli@gmail.com>
Cc:     Justin Chen <justinpopo6@gmail.com>, linux-usb@vger.kernel.org,
        linux-kernel@vger.kernel.org, vkoul@kernel.org, kishon@ti.com,
        linux-phy@lists.infradead.org, alcooperx@gmail.com,
        bcm-kernel-feedback-list@broadcom.com, justin.chen@broadcom.com
Subject: Re: [PATCH] MAINTAINERS: Update maintainers for broadcom USB
Message-ID: <Y0B8X1q0twk5aJt0@kroah.com>
References: <1665098469-19008-1-git-send-email-justinpopo6@gmail.com>
 <Yz/G0jQxc4c2gzhl@kroah.com>
 <CAJx26kUTzBeNkV_=gEeUYaatBwugT1uFH_b_ggq-fXaJDRBMqQ@mail.gmail.com>
 <Yz/Oik0uXXo0uGk6@kroah.com>
 <CAJx26kVL4nYL2fbHd31ZqpXxEos-nyQ2-GSZbL6FUa5ztAbxXw@mail.gmail.com>
 <Yz/UqtGD/dthxYJ2@kroah.com>
 <3d74b5cf-0f50-ac27-aa21-210507f41858@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3d74b5cf-0f50-ac27-aa21-210507f41858@gmail.com>
Precedence: bulk

On Fri, Oct 07, 2022 at 11:45:04AM -0700, Florian Fainelli wrote:
> 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@linuxfoundation.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@linuxfoundation.org> wrote:
> > > > > > 
> > > > > > On Thu, Oct 06, 2022 at 04:21:09PM -0700, justinpopo6@gmail.com wrote:
> > > > > > > From: Justin Chen <justinpopo6@gmail.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 :)?

It doesn't really matter much, but we are seeing more and more email
validation being added and required over time for people sending
patches.  So it's up to you and your corporate rules as to what you want
to do.

thanks,

greg k-h