netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: jeff@garzik.org
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: [E1000-devel] [PATCH 4/4] Intel ethernet adapter: Update MAINTAINERS
Date: Mon, 03 Mar 2008 14:48:22 -0800	[thread overview]
Message-ID: <47CC8036.6040400@intel.com> (raw)
In-Reply-To: <20080303223747.16344.11861.stgit@localhost.localdomain>

Auke Kok wrote:
> Another team member unfortunately left: update MAINTAINERS.
> 
> Condense the 3 lists down to a single list for all our drivers.
> 
> Point to our new sourceforge index page which is slightly
> better navigateable than the sf.net project page.
> 
> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
> ---
> 
>  MAINTAINERS |   32 ++++----------------------------
>  1 files changed, 4 insertions(+), 28 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 2333255..a945724 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2033,43 +2033,19 @@ M:	kernel@wantstofly.org
>  L:	netdev@vger.kernel.org
>  S:	Maintained
>  
> -INTEL PRO/100 ETHERNET SUPPORT
> +INTEL ETHERNET DRIVERS (e100/e1000/e1000e/igb/ixgb/ixgbe)
>  P:	Auke Kok
>  M:	auke-jan.h.kok@intel.com
>  P:	Jesse Brandeburg
>  M:	jesse.brandeburg@intel.com
>  P:	Jeff Kirsher
>  M:	jeffrey.t.kirsher@intel.com
> +P:	Bruce Allan
> +M:	bruce.w.allan@intel.com
>  P:	John Ronciak
>  M:	john.ronciak@intel.com
>  L:	e1000-devel@lists.sourceforge.net
> -W:	http://sourceforge.net/projects/e1000/
> -S:	Supported
> -
> -INTEL PRO/1000 GIGABIT ETHERNET SUPPORT
> -P:	Auke Kok
> -M:	auke-jan.h.kok@intel.com
> -P:	Jesse Brandeburg
> -M:	jesse.brandeburg@intel.com
> -P:	Jeff Kirsher
> -M:	jeffrey.t.kirsher@intel.com
> -P:	John Ronciak
> -M:	john.ronciak@intel.com
> -L:	e1000-devel@lists.sourceforge.net
> -W:	http://sourceforge.net/projects/e1000/
> -S:	Supported
> -
> -INTEL PRO/10GbE SUPPORT
> -P:	Ayyappan Veeraiyan
> -M:	ayyappan.veeraiyan@intel.com
> -P:	Auke Kok
> -M:	auke-jan.h.kok@intel.com
> -P:	Jesse Brandeburg
> -M:	jesse.brandeburg@intel.com
> -P:	John Ronciak
> -M:	john.ronciak@intel.com
> -L:	e1000-devel@lists.sourceforge.net
> -W:	http://sourceforge.net/projects/e1000/
> +W:	http://e1000.sourceforge.net/
>  S:	Supported
>  
>  INTEL PRO/WIRELESS 2100 NETWORK CONNECTION SUPPORT

ok, I should have reordered this.

patch 1, 2 and 4 are for upstream-fixes
patch #3 is for #upstream

thanks,

Auke


  reply	other threads:[~2008-03-03 22:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-03 22:37 [PATCH 1/4] e100: Do suspend/shutdown like e1000 Auke Kok
2008-03-03 22:37 ` [PATCH 2/4] [RFC] e1000: make ioport free for supported devices Auke Kok
2008-03-05 11:32   ` Jeff Garzik
2008-03-06 19:35     ` [E1000-devel] " Kok, Auke
2008-03-03 22:37 ` [PATCH 3/4] ixgbe: fix typo in speed mesage Auke Kok
2008-03-03 22:37 ` [PATCH 4/4] Intel ethernet adapter: Update MAINTAINERS Auke Kok
2008-03-03 22:48   ` Kok, Auke [this message]
2008-03-05 12:18 ` [PATCH 1/4] e100: Do suspend/shutdown like e1000 Jeff Garzik
2008-03-05 12:18   ` Jeff Garzik

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=47CC8036.6040400@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).