public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Ed Tomlinson <edt@aei.ca>, Pete Zaitcev <zaitcev@redhat.com>,
	Matthew Dharm <mdharm-kernel@one-eyed-alien.net>,
	"Randy.Dunlap" <rddunlap@osdl.org>, Adrian Bunk <bunk@stusta.de>,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: RFC: [2.6 patch] let BLK_DEV_UB depend on EMBEDDED
Date: Mon, 20 Dec 2004 07:35:08 -0800	[thread overview]
Message-ID: <20041220153508.GB17121@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0412201026390.1358-100000@ida.rowland.org>

On Mon, Dec 20, 2004 at 10:28:05AM -0500, Alan Stern wrote:
> On Mon, 20 Dec 2004, Ed Tomlinson wrote:
> 
> > Its not that they just enable it.  Its that it has side effects.  I enable it to support
> > one device - it then 'devnaps' other devices that usbstorage supports _much_
> > better.  Is there some way it could work in reverse.  eg. let ub bind only if 
> > usbstorage does not, possibly making usbstorage a _little_ more conservative
> > if ub is present?
> 
> Unfortunately there isn't any way to define which driver should bind to a 
> device, if they are both capable of controlling it.  Maybe there should 
> be.  It might not be too hard to add a sysfs interface for that sort of 
> thing.

We are working on it...

thanks,

greg k-h

  reply	other threads:[~2004-12-20 15:41 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20  0:16 RFC: [2.6 patch] let BLK_DEV_UB depend on EMBEDDED Adrian Bunk
2004-12-20  0:29 ` Pete Zaitcev
2004-12-20  0:31 ` Greg KH
2004-12-20  1:35   ` Adrian Bunk
2004-12-20  4:51     ` Pete Zaitcev
2004-12-20  5:09       ` Randy.Dunlap
2004-12-20  6:20         ` Matthew Dharm
2004-12-20  6:37           ` Pete Zaitcev
2004-12-20  7:28             ` [linux-usb-devel] " Phil Dibowitz
2004-12-20  8:09             ` Matthew Dharm
2004-12-20  8:25               ` [linux-usb-devel] " Phil Dibowitz
2004-12-20  8:44               ` Pete Zaitcev
2004-12-20  8:59                 ` [linux-usb-devel] " Phil Dibowitz
2004-12-20 12:02             ` Ed Tomlinson
2004-12-20 15:28               ` [linux-usb-devel] " Alan Stern
2004-12-20 15:35                 ` Greg KH [this message]
2004-12-20 20:46                 ` Lee Revell
2004-12-22  8:10             ` Rob Browning
2004-12-23  1:45               ` Theodore Ts'o
2004-12-20  6:43           ` David Brownell
2004-12-20  7:06             ` Pete Zaitcev
2004-12-20 16:03               ` [linux-usb-devel] " David Brownell
2004-12-20  6:30         ` Pete Zaitcev
2004-12-20 15:25           ` [linux-usb-devel] " Alan Stern
2004-12-23  2:40   ` RFC: [2.6 patch] let BLK_DEV_UB depend on USB_STORAGE=n Adrian Bunk
2005-01-19 22:07     ` Greg KH
2005-01-20  2:49       ` Matthew Dharm
2005-01-21  0:04         ` Greg KH
2005-01-24 11:48       ` David Woodhouse
2005-01-24 17:49         ` Pete Zaitcev

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=20041220153508.GB17121@kroah.com \
    --to=greg@kroah.com \
    --cc=bunk@stusta.de \
    --cc=edt@aei.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mdharm-kernel@one-eyed-alien.net \
    --cc=rddunlap@osdl.org \
    --cc=stern@rowland.harvard.edu \
    --cc=zaitcev@redhat.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