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 01:09:55 -0700	[thread overview]
Message-ID: <1375344595.2034.38.camel@joe-AO722> (raw)
In-Reply-To: <20130801075656.GA8074@kroah.com>

On Thu, 2013-08-01 at 15:56 +0800, Greg KH wrote:
> On Thu, Aug 01, 2013 at 12:48:48AM -0700, Joe Perches wrote:
> > There are several drivers in drivers/net/usb/ that
> > do not have specific MAINTAINERS that should have
> > emails forwarded to the linux-usb mailing list.

> > diff --git a/MAINTAINERS b/MAINTAINERS
[]
> > +USB NETWORKING DRIVERS
> > +L:	linux-usb@vger.kernel.org
> > +S:	Odd Fixes
> > +F:	drivers/net/usb/
> 
> But netdev is the one that applies these patches, not linux-usb, so this
> isn't correct either.
> 
> sorry,

Lots of "maintainers" don't apply patches.

This is simply a means to forward patches to
relevant lists that may have reviewers that care
about changes to certain files.

You suggested that linux-usb should get copies
of these patches.

These files are not marked as "Maintained", just
"Odd fixes".  I suppose these could be marked
"Orphan" instead.

You have a suggestion otherwise?


  reply	other threads:[~2013-08-01  8:10 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 [this message]
2013-08-02  3:30       ` Greg KH
2013-08-02  3:50         ` Joe Perches
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=1375344595.2034.38.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®