Hi!

> > Let's assume (yes, I know what that means) that 2.4.0
> > will be released soon... what do we need to focus on
> > in the next few (or many) weeks to assure:
> > 
> > - decent behavior of USB (minimal oops/bug reports)
> > - satisfied users (at least of devices that we have support for)
> [stuff snipped]
> In all this discussion of usbdevfs (which I do understand is key
> infrastructure) and its future, I think that this point got missed.
> 
> Things that I think need to be done for 2.4.0:
> * Get usb-storage out of experimental state, and make it build and work
> in the kernel

It seems to be as easy as: Matt, do you have something strong against
this? Works-for-me (tm).
 
--- clean/drivers/usb/Config.in Thu Apr 27 10:05:48 2000
+++ linux/drivers/usb/Config.in Thu Apr 27 10:03:20 2000
@@ -42,7 +42,7 @@
    dep_tristate '  USB Kodak DC-2xx Camera support' CONFIG_USB_DC2XX $CONFIG_USB
    if [ "$CONFIG_EXPERIMENTAL" = "y" ]; then
           dep_tristate '  USB Mustek MDC800 Digital Camera support (EXPERIMENTAL)' 
CONFIG_USB_MDC800 $CONFIG_USB
-      dep_tristate '  USB Mass Storage support (EXPERIMENTAL)' CONFIG_USB_STORAGE 
$CONFIG_USB m
+      dep_tristate '  USB Mass Storage support (EXPERIMENTAL)' CONFIG_USB_STORAGE 
+$CONFIG_USB
       if [ "$CONFIG_USB_STORAGE" != "n" ]; then
          bool '    USB Mass Storage verbose debug' CONFIG_USB_STORAGE_DEBUG
       fi

                                                                Pavel
-- 
I'm [EMAIL PROTECTED] "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents me at [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to