aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/hid/usbhid
diff options
context:
space:
mode:
authorJiri Kosina <jkosina@suse.cz>2007-04-29 07:14:56 -0400
committerJiri Kosina <jkosina@suse.cz>2007-04-29 07:14:56 -0400
commitf61c9127b9840661244b1b6571e4304a7f0b5c73 (patch)
tree1faa5b95c6fb176b5306e38fbdc58478f1e02676 /drivers/hid/usbhid
parent876b9276b993723f7a74d55b3b49b9186f05d09d (diff)
USB HID: don't warn on idVendor == 0
It turns out that there are broken devices out there that incorrectly report VID/PID as 0x000, see http://lkml.org/lkml/2007/4/27/496 Therefore we should not confuse users by dumping warnings and stacktraces in such situation. It is not possible to add quirks for such horribly broken devices, but currently that's not needed. Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/hid/usbhid')
-rw-r--r--drivers/hid/usbhid/hid-quirks.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/hid/usbhid/hid-quirks.c b/drivers/hid/usbhid/hid-quirks.c
index 27188bd1e851..17a87555e32f 100644
--- a/drivers/hid/usbhid/hid-quirks.c
+++ b/drivers/hid/usbhid/hid-quirks.c
@@ -477,8 +477,6 @@ static struct hid_blacklist *usbhid_exists_dquirk(const u16 idVendor,
477 struct quirks_list_struct *q; 477 struct quirks_list_struct *q;
478 struct hid_blacklist *bl_entry = NULL; 478 struct hid_blacklist *bl_entry = NULL;
479 479
480 WARN_ON(idVendor == 0);
481
482 list_for_each_entry(q, &dquirks_list, node) { 480 list_for_each_entry(q, &dquirks_list, node) {
483 if (q->hid_bl_item.idVendor == idVendor && 481 if (q->hid_bl_item.idVendor == idVendor &&
484 q->hid_bl_item.idProduct == idProduct) { 482 q->hid_bl_item.idProduct == idProduct) {