Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Justin Chen <justinpopo6@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	vkoul@kernel.org, kishon@ti.com, linux-phy@lists.infradead.org,
	f.fainelli@gmail.com, alcooperx@gmail.com,
	bcm-kernel-feedback-list@broadcom.com, justin.chen@broadcom.com
Subject: Re: [PATCH] MAINTAINERS: Update maintainers for broadcom USB
Date: Fri, 7 Oct 2022 09:26:34 +0200	[thread overview]
Message-ID: <Yz/UqtGD/dthxYJ2@kroah.com> (raw)
In-Reply-To: <CAJx26kVL4nYL2fbHd31ZqpXxEos-nyQ2-GSZbL6FUa5ztAbxXw@mail.gmail.com>

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?  :)

thanks,

greg k-h

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  reply	other threads:[~2022-10-07  7:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 23:21 [PATCH] MAINTAINERS: Update maintainers for broadcom USB justinpopo6
2022-10-07  3:37 ` Florian Fainelli
2022-10-07  6:27 ` Greg KH
2022-10-07  6:46   ` Justin Chen
2022-10-07  7:00     ` Greg KH
2022-10-07  7:19       ` Justin Chen
2022-10-07  7:26         ` Greg KH [this message]
2022-10-07 18:45           ` Florian Fainelli
2022-10-07 19:22             ` Greg KH

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=Yz/UqtGD/dthxYJ2@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alcooperx@gmail.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=f.fainelli@gmail.com \
    --cc=justin.chen@broadcom.com \
    --cc=justinpopo6@gmail.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=vkoul@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