All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: netdev <netdev@vger.kernel.org>,
	"David Miller" <davem@davemloft.net>,
	"Michael Chan" <michael.chan@broadcom.com>,
	bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"Hauke Mehrtens" <hauke@hauke-m.de>
Subject: Re: [PATCH net] MAINTAINERS: Gary Zambrano's email is bouncing
Date: Sat, 17 Sep 2016 16:57:10 -0700	[thread overview]
Message-ID: <1474156630.1954.12.camel@perches.com> (raw)
In-Reply-To: <d9aaaf17-4d82-a8f0-d257-aba1e78704e8@gmail.com>

On Sat, 2016-09-17 at 16:38 -0700, Florian Fainelli wrote:
> 2016-09-17 16:23 GMT-07:00 Joe Perches <joe@perches.com>:
> > On Sat, 2016-09-17 at 16:17 -0700, Florian Fainelli wrote:
> > > The list does not accept public subscribers, so this is the correct
> > > entry to use.
> > Then M: is definitely _not_ the correct entry for this
> > and it should be:
> > L: bcm-kernel-feedback-list@broadcom.com (subscribers-only)

> Olof indicated otherwise, so who is right here?https://www.spinics.net/lists/arm-kernel/msg512572.html

> prompting to this patch series:
> http://linux-arm-kernel.infradead.narkive.com/CRyvGOKd/patch-maintainers-change-l-to-

This hasn't been applied to -next, and I looked at the 
existing L: entries.

No worries here either if it's an exploder and not a mailing list.

Pity it's not called something like bcm-linux-drivers@broadcom.com
if it's really an exploder.

  reply	other threads:[~2016-09-17 23:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 22:27 [PATCH net] MAINTAINERS: Gary Zambrano's email is bouncing Florian Fainelli
2016-09-17 22:51 ` Joe Perches
2016-09-17 23:17   ` Florian Fainelli
2016-09-17 23:23     ` Joe Perches
2016-09-17 23:38       ` Florian Fainelli
2016-09-17 23:57         ` Joe Perches [this message]
2016-09-17 23:39     ` Michael Chan
2016-09-19 19:54       ` Florian Fainelli
2016-09-19 20:03         ` Michael Chan

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=1474156630.1954.12.camel@perches.com \
    --to=joe@perches.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.