All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Indan Zupancic" <indan@nul.nu>
To: "Jeff Garzik" <jeff@garzik.org>, duncan.sands@free.fr
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	"LKML" <linux-kernel@vger.kernel.org>,
	gregkh@suse.de, linux-usb-devel@lists.sourceforge.net
Subject: Re: [git patch] move USB net drivers to drivers/net
Date: Thu, 10 May 2007 14:12:47 +0200 (CEST)	[thread overview]
Message-ID: <1358.81.207.0.53.1178799167.squirrel@secure.samage.net> (raw)
In-Reply-To: <20070510013855.GA3402@havoc.gtf.org>

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@garzik.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/?

Greetings,

Indan



  reply	other threads:[~2007-05-10 12:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-10  1:38 [git patch] move USB net drivers to drivers/net Jeff Garzik
2007-05-10 12:12 ` Indan Zupancic [this message]
2007-05-10 12:27   ` Duncan Sands
2007-05-10 16:12 ` [another git " Jan Engelhardt
2007-08-17 10:45   ` Jan Engelhardt

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=1358.81.207.0.53.1178799167.squirrel@secure.samage.net \
    --to=indan@nul.nu \
    --cc=akpm@linux-foundation.org \
    --cc=duncan.sands@free.fr \
    --cc=gregkh@suse.de \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.