netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Jeff Garzik <jeff@garzik.org>
Cc: Peter Korsgaard <jacmet@sunsite.dk>,
	netdev@vger.kernel.org, Petko Manolov <petkan@nucleusys.com>,
	Greg KH <greg@kroah.com>
Subject: Re: [PATCH] Update MAINTAINERS for USB network devices
Date: Wed, 27 Jun 2007 01:54:15 -0700	[thread overview]
Message-ID: <200706270154.16022.david-b@pacbell.net> (raw)
In-Reply-To: <46821E80.8080105@garzik.org>

On Wednesday 27 June 2007, Jeff Garzik wrote:
> Peter Korsgaard wrote:
> > Questions regarding the USB network drivers should now go to netdev.
> > 
> > Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
> > ---
> >  MAINTAINERS |   13 +++++--------
> >  1 file changed, 5 insertions(+), 8 deletions(-)
> > 
> > Index: linux-2.6.22-rc6/MAINTAINERS
> > ===================================================================
> > --- linux-2.6.22-rc6.orig/MAINTAINERS
> > +++ linux-2.6.22-rc6/MAINTAINERS
> > @@ -3610,15 +3610,14 @@
> >  USB CDC ETHERNET DRIVER
> >  P:	Greg Kroah-Hartman

I think that may refer to the old cdc ethernet driver
though ... Greg?  The new one, in the usbnet framework,
is a very different beast...


> >  M:	greg@kroah.com
> > -L:	linux-usb-users@lists.sourceforge.net
> > -L:	linux-usb-devel@lists.sourceforge.net
> > +L:	netdev@vger.kernel.org
> >  S:	Maintained
> >  W:	http://www.kroah.com/linux-usb/
> >  
> >  USB DAVICOM DM9601 DRIVER
> >  P:	Peter Korsgaard
> >  M:	jacmet@sunsite.dk
> > -L:	linux-usb-devel@lists.sourceforge.net
> > +L:	netdev@vger.kernel.org
> >  W:	http://www.linux-usb.org/usbnet
> >  S:	Maintained
> >  
> > @@ -3702,8 +3701,7 @@
> >  USB PEGASUS DRIVER
> >  P:	Petko Manolov
> >  M:	petkan@users.sourceforge.net
> > -L:	linux-usb-users@lists.sourceforge.net
> > -L:	linux-usb-devel@lists.sourceforge.net
> > +L:	netdev@vger.kernel.org
> >  W:	http://pegasus2.sourceforge.net/
> >  S:	Maintained
> >  
> > @@ -3717,8 +3715,7 @@
> >  USB RTL8150 DRIVER
> >  P:	Petko Manolov
> >  M:	petkan@users.sourceforge.net
> > -L:	linux-usb-users@lists.sourceforge.net
> > -L:	linux-usb-devel@lists.sourceforge.net
> > +L:	netdev@vger.kernel.org
> >  W:	http://pegasus2.sourceforge.net/
> >  S:	Maintained
> >  
> > @@ -3829,7 +3826,7 @@
> >  USB "USBNET" DRIVER FRAMEWORK
> >  P:	David Brownell
> >  M:	dbrownell@users.sourceforge.net
> > -L:	linux-usb-devel@lists.sourceforge.net
> > +L:	netdev@vger.kernel.org
> >  W:	http://www.linux-usb.org/usbnet
> >  S:	Maintained
> 
> Quite true, but for courtesy's sake you should keep the relevant 
> maintainers in the loop, and get their ACKs, when you start changing 
> their MAINTAINERS entries.

Acked-by-Me.


> 
> 	Jeff
> 
> 
> 



  parent reply	other threads:[~2007-06-27  9:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-27  7:53 [PATCH] Update MAINTAINERS for USB network devices Peter Korsgaard
2007-06-27  8:23 ` Jeff Garzik
2007-06-27  8:42   ` Peter Korsgaard
2007-06-27  8:54   ` David Brownell [this message]
2007-06-27 14:44     ` Greg KH
2007-06-27 15:12       ` David Brownell
2007-06-27 19:18       ` Peter Korsgaard
2007-07-02 12:25         ` Jeff Garzik
2007-06-27 10:44   ` Petko Manolov

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=200706270154.16022.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=greg@kroah.com \
    --cc=jacmet@sunsite.dk \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=petkan@nucleusys.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 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).