linux-kernel - Re: [git patch] move USB net drivers to drivers/net

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: <200705101427.30990.duncan.sands@free.fr>
Date:	Thu, 10 May 2007 14:27:26 +0200
From:	Duncan Sands <duncan.sands@...e.fr>
To:	"Indan Zupancic" <indan@....nu>
Cc:	"Jeff Garzik" <jeff@...zik.org>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"LKML" <linux-kernel@...r.kernel.org>, gregkh@...e.de,
	linux-usb-devel@...ts.sourceforge.net
Subject: Re: [git patch] move USB net drivers to drivers/net

On Thursday 10 May 2007 14:12:47 Indan Zupancic wrote:
> Hello,
> 
> On Thu, May 10, 2007 03:38, Jeff Garzik wrote:
> >
> > This was ACK'd by Greg, as you see in the sign-offs.  See the commit
> > below for rationale.
> >
> > USB is now treated like other buses, for network drivers:
> > * USB network driver patches should go to me and netdev
> > * Just like in PCI or PCMCIA land, bus-specific code may
> >   originate from the USB side of the house (Greg's tree).
> >
> >
> >
> > Please pull from 'usb-move' branch of
> > master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git usb-move
> >
> > to receive the following update:
> >
> >
> > commit 5b2fc499917e5897a13add780e181b4cef197072
> > Author: Jeff Garzik <jeff@...zik.org>
> > Date:   Wed May 9 21:31:55 2007 -0400
> >
> >     Move USB network drivers to drivers/net/usb.
> >
> >     It is preferable to group drivers by usage (net, scsi, ATA, ...) than
> >     by bus.  When reviewing drivers, the [PCI|USB|PCMCIA|...] maintainer
> >     is probably less qualified on networking issues than a networking
> >     maintainer.  Also, from a practical standpoint, chips often
> >     appear on multiple buses, which is why we do not put drivers into
> >     drivers/pci/net.
> 
> What about drivers/usb/atm/?

I don't mind if it moves to drivers/atm/, though I don't see the point of it.

Best wishes,

Duncan.
-
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/