mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-usb <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add separate section for USB NETWORKING DRIVERS
Date: Thu, 01 Aug 2013 20:50:10 -0700	[thread overview]
Message-ID: <1375415410.2034.100.camel@joe-AO722> (raw)
In-Reply-To: <20130802033033.GA2658@kroah.com>

On Fri, 2013-08-02 at 11:30 +0800, Greg KH wrote:
> On Thu, Aug 01, 2013 at 01:09:55AM -0700, Joe Perches wrote:
> > Lots of "maintainers" don't apply patches.
> I have no idea what you are meaning here.

Just that maintainers aren't necessarily appliers.
In fact, most aren't.

> Add netdev to the L: list as well.

I don't think it's necessary.
get_maintainers already shows that via the
NETWORKING DRIVERS section F: drivers/net/

Maybe adding
	W:	http://www.linux-usb.org/usbnet
might be useful, but it seems pretty out of date.

btw: This is a similar section to what I suggested.
     No named "maintainer"

NETWORKING DRIVERS
L:	netdev@vger.kernel.org
W:	http://www.linuxfoundation.org/en/Net
Q:	http://patchwork.ozlabs.org/project/netdev/list/
T:	git git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
T:	git git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
S:	Odd Fixes
F:	drivers/net/



  reply	other threads:[~2013-08-02  3:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1375316960686@kroah.org>
2013-08-01  7:48 ` Joe Perches
2013-08-01  7:56   ` Greg KH
2013-08-01  8:09     ` Joe Perches
2013-08-02  3:30       ` Greg KH
2013-08-02  3:50         ` Joe Perches [this message]
2013-08-02  4:01           ` Greg KH
2013-08-02  4:03 ` [PATCH resend] " Joe Perches
2013-08-02  7:36   ` 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=1375415410.2034.100.camel@joe-AO722 \
    --to=joe@perches.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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

all inboxes | Powered by JetHome®