summaryrefslogtreecommitdiffstats
path: root/COPYING
diff options
context:
space:
mode:
authorHenk <Henk.Vergonet@gmail.com>2005-12-30 19:41:11 +0100
committerGreg Kroah-Hartman <gregkh@suse.de>2006-01-31 17:23:37 -0800
commit8e2ce4f92a0f34e8c3316ec58fd6eb6aa282448e (patch)
treecbb996b43ecc036d69d32bbdcf61e607c9dc676f /COPYING
parent09c280a24650ff74e713742e94120fdf7765cda8 (diff)
downloadkernel-crypto-8e2ce4f92a0f34e8c3316ec58fd6eb6aa282448e.tar.gz
kernel-crypto-8e2ce4f92a0f34e8c3316ec58fd6eb6aa282448e.tar.xz
kernel-crypto-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 <henk.vergonet@gmail.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions