From: Phil Dibowitz <phil@ipom.com>
To: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
"Randy.Dunlap" <rddunlap@osdl.org>, Adrian Bunk <bunk@stusta.de>,
Greg KH <greg@kroah.com>,
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 00:25:56 -0800 [thread overview]
Message-ID: <41C68C94.7080805@ipom.com> (raw)
In-Reply-To: <20041220080951.GA24728@one-eyed-alien.net>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
Matthew Dharm wrote:
>
> The best idea I have is to hide CONFIG_BLK_DEV_UB behind
> CONFIG_EXPERIMENTAL.
As a long-term solution, this obviously won't work, but I think it's a
_very_ good solution for now. UB _is_ expiramental at this point. It
still has it's issues, and per Pete is still not to be used unless you
really know what you're doing.
That makes it expiramental to me.
> The next-best idea I have is to make UB print out some sort of warning
> message at startup.
>
> Neither of these ideas is very good, I'll admit.
This is decent idea. Some "Warning: UB enabled - your usb-storage
devices may not work properly!" type thing on loading can't hurt.
Not the cleanest thing in the world, but look how well it worked for the
unusual_devs cleanups.
--
Phil Dibowitz phil@ipom.com
Freeware and Technical Pages Insanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
- Benjamin Franklin, 1759
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-12-20 8:29 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 ` Phil Dibowitz [this message]
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
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=41C68C94.7080805@ipom.com \
--to=phil@ipom.com \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--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=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