[patch 03/03] add EXPORT_SYMBOL_GPL_FUTURE() to USB subsystem

From: Greg KH
Date: Wed Feb 08 2006 - 13:49:26 EST

The USB core symbols will be converted to GPL-only in a few years. Mark
this as such and update the documentation explaining why, and provide a
pointer for developers to receive help if they need it.

Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxx>
Documentation/feature-removal-schedule.txt | 19 +++++++++++++++++++
drivers/usb/core/driver.c | 6 +++---
2 files changed, 22 insertions(+), 3 deletions(-)

--- gregkh-2.6.orig/drivers/usb/core/driver.c
+++ gregkh-2.6/drivers/usb/core/driver.c
@@ -381,7 +381,7 @@ const struct usb_device_id *usb_match_id

return NULL;

int usb_device_match(struct device *dev, struct device_driver *drv)
@@ -449,7 +449,7 @@ int usb_register_driver(struct usb_drive

return retval;

* usb_deregister - unregister a USB driver
@@ -472,4 +472,4 @@ void usb_deregister(struct usb_driver *d

--- gregkh-2.6.orig/Documentation/feature-removal-schedule.txt
+++ gregkh-2.6/Documentation/feature-removal-schedule.txt
@@ -171,3 +171,22 @@ Why: The ISA interface is faster and sho
probing is also known to cause trouble in at least one case (see
bug #5889.)
Who: Jean Delvare <khali@xxxxxxxxxxxx>
+What: USB driver API moves to EXPORT_SYMBOL_GPL
+When: Febuary 2008
+Files: include/linux/usb.h, drivers/usb/core/driver.c
+Why: The USB subsystem has changed a lot over time, and it has been
+ possible to create userspace USB drivers using usbfs/libusb/gadgetfs
+ that operate as fast as the USB bus allows. Because of this, the USB
+ subsystem will not be allowing closed source kernel drivers to
+ register with it, after this grace period is over. If anyone needs
+ any help in converting their closed source drivers over to use the
+ userspace filesystems, please contact the
+ linux-usb-devel@xxxxxxxxxxxxxxxxxxxxx mailing list, and the developers
+ there will be glad to help you out.
+Who: Greg Kroah-Hartman <gregkh@xxxxxxx>
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/