linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@wirex.com>
To: jt@hpl.hp.com
Cc: Dag Brattli <dag@brattli.net>,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] patch-2.4.2-irda1 (irda-usb)
Date: Tue, 27 Feb 2001 21:40:46 -0800	[thread overview]
Message-ID: <20010227214046.A10265@wirex.com> (raw)
In-Reply-To: <20010227093329.A10482@wirex.com> <200102272032.UAA74232@tepid.osl.fast.no> <20010227135810.E910@wirex.com> <20010227184109.B6898@bougret.hpl.hp.com>
In-Reply-To: <20010227184109.B6898@bougret.hpl.hp.com>; from jt@bougret.hpl.hp.com on Tue, Feb 27, 2001 at 06:41:09PM -0800

On Tue, Feb 27, 2001 at 06:41:09PM -0800, Jean Tourrilhes wrote:
> 
> 	First thanks for Dag for bringing me into the conversation. I
> may add my little bit of spice, especially that I was the one pushing
> for having the driver in .../drivers/net/irda.
> 	By the way, Greg, sorry if I hurt your feeling, I don't want
> to put down any of the great work that has been done on the USB stack.

Thanks, but it didn't bother me, or hurt any of my feelings at all.  I
just wanted to point out that all of the other usb drivers (with 2
exceptions) reside in the drivers/usb directory, and I didn't know if
you knew that.

(the exceptions are the input drivers, which are part of the input core,
and the cpia video driver, which has the parallel port and the usb
driver all together in one file.)

> 	My feeling is that devices are mostly defined by their higher
> level interface, because this is what is closer to the user.
> 	If I look at a Pcmcia Ethernet card, I will tend to associate
> more with a PCI Ethernet card rather than a Pcmcia SCSI card. Both
> card have the same high level interface (TCP/IP) even if their low
> level interface is different (Pcmcia, PCI).
> 	People tend to agree with that, and that's why you have
> directories called drivers/net, drivers/scsi and driver/sound, rather
> that drivers/pci, drivers/isa, drivers/mca and drivers/pcmcia.

This argument has been discussed in the past (see the linux-usb-devel
and linux-kernel mailing list archives) but from what I remember, Linus
and others wanted them all to stay in the drivers/usb directory for now.

Personally I don't care either way, but it has been easier to do usb
core changes (such as the hotplug interface changes that I suggested for
your driver) with all of the drivers in one place, not that I can't do a
recursive grep :)

thanks,

greg k-h

-- 
greg@(kroah|wirex).com
http://immunix.org/~greg

  reply	other threads:[~2001-02-28  5:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27  8:29 [patch] patch-2.4.2-irda1 (irda-usb) Dag Brattli
2001-02-27 17:33 ` Greg KH
2001-02-27 20:32   ` Dag Brattli
2001-02-27 21:58     ` Greg KH
2001-02-28  2:41       ` Jean Tourrilhes
2001-02-28  5:40         ` Greg KH [this message]
2001-02-28  3:43 Dunlap, Randy

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=20010227214046.A10265@wirex.com \
    --to=greg@wirex.com \
    --cc=dag@brattli.net \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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;
as well as URLs for NNTP newsgroup(s).