linux-kernel - Re: [PATCH] MAINTAINERS: Add separate section for USB NETWORKING DRIVERS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1375344595.2034.38.camel@joe-AO722>
Date:	Thu, 01 Aug 2013 01:09:55 -0700
From:	Joe Perches <joe@...ches.com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	linux-usb <linux-usb@...r.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Add separate section for USB NETWORKING
 DRIVERS

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@...r.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?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/