diff options
| author | Henk <[email protected]> | 2005-12-30 18:41:11 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2006-02-01 01:23:37 +0000 |
| commit | 8e2ce4f92a0f34e8c3316ec58fd6eb6aa282448e (patch) | |
| tree | cbb996b43ecc036d69d32bbdcf61e607c9dc676f /drivers/usb/class/cdc-acm.c | |
| parent | [PATCH] USB: ftdi: Two new ATIK based USB astronomical CCD cameras (diff) | |
| download | kernel-8e2ce4f92a0f34e8c3316ec58fd6eb6aa282448e.tar.gz kernel-8e2ce4f92a0f34e8c3316ec58fd6eb6aa282448e.zip | |
[PATCH] drivers/usb/input/yealink.c: Cleanup device matching code
This should fix things mentioned below:
"I was curious why my firewall was loading a 'phone driver'.
It turns out that the probing in the yealink driver is
a little too assuming..
static struct usb_device_id usb_table [] = {
{ USB_INTERFACE_INFO(USB_CLASS_HID, 0, 0) },
{ }
};
So it picked up my UPS, and loaded the driver.
Whilst no harm came, because it later checks the vendor/product IDs,
this driver should probably be rewritten to only probe
for the device IDs it actually knows about.
Dave"
Signed-off-by: Henk Vergonet <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'drivers/usb/class/cdc-acm.c')
0 files changed, 0 insertions, 0 deletions
