All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Florian Fainelli <f.fainelli@gmail.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, michael.chan@broadcom.com,
	bcm-kernel-feedback-list@broadcom.com, zajec5@gmail.com,
	hauke@hauke-m.de
Subject: Re: [PATCH net] MAINTAINERS: Gary Zambrano's email is bouncing
Date: Sat, 17 Sep 2016 15:51:49 -0700	[thread overview]
Message-ID: <1474152709.1954.8.camel@perches.com> (raw)
In-Reply-To: <1474151235-16558-1-git-send-email-f.fainelli@gmail.com>

On Sat, 2016-09-17 at 15:27 -0700, Florian Fainelli wrote:
> Gary has not been with Broadcom for some time now, replace his address
> with the internal mailing-list used for other entries.
> 
> > Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> --- 
> Michael,
> 
> Since this is an old driver, not sure who could step up as a maintainer
> for b44?
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
[]
> @@ -2500,8 +2500,8 @@ S:	Supported

> F:	kernel/bpf/
>  
>  BROADCOM B44 10/100 ETHERNET DRIVER
> -M:	Gary Zambrano <zambrano@broadcom.com>
>  L:	netdev@vger.kernel.org
> +M:	bcm-kernel-feedback-list@broadcom.com
>  S:	Supported
>  F:	drivers/net/ethernet/broadcom/b44.*

Without an actual maintainer, this should really be
orphan and not supported.

And the M: bcm-kernel-feedback-list@ should be L:

BCM4401 NICs are essentially from 2002.

Does anyone really use these any longer with a
current distribution or kernel version?

  reply	other threads:[~2016-09-17 22:51 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 [this message]
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
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=1474152709.1954.8.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.