public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
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, 1 Aug 2013 15:56:56 +0800	[thread overview]
Message-ID: <20130801075656.GA8074@kroah.com> (raw)
In-Reply-To: <1375343328.2034.34.camel@joe-AO722>

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.
> 
> Add a section for those drivers.
> 
> Signed-off-by: Joe Perches <joe@perches.com>
> ---
> > In the future, you do not need to send drivers/net/usb/ patches to me,
> > netdev and the linux-usb mailing lists should be sufficient.
> 
> I should have done this in the first patch.
> Oh well...
> 
>  MAINTAINERS | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d83f70f..4af7539 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8656,6 +8656,11 @@ T:	git git://git.alsa-project.org/alsa-kernel.git
>  S:	Maintained
>  F:	sound/usb/midi.*
>  
> +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,

greg k-h

  reply	other threads:[~2013-08-01  7:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1375316960686@kroah.org>
2013-08-01  7:48 ` [PATCH] MAINTAINERS: Add separate section for USB NETWORKING DRIVERS Joe Perches
2013-08-01  7:56   ` Greg KH [this message]
2013-08-01  8:09     ` Joe Perches
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=20130801075656.GA8074@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --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