Searched hist:"2 a0f9c4c452298da89b67060c7ca034ef7836aa9" (Results 1 – 2 of 2) sorted by relevance
| /linux/drivers/input/mouse/ |
| H A D | inport.c | diff 2a0f9c4c452298da89b67060c7ca034ef7836aa9 Fri Nov 02 03:19:15 CET 2007 Helge Deller <deller@gmx.de> Input: inport, logibm - use KERN_INFO when reporting missing mouse
Many mouse drivers are often compiled (e.g. in Linux distributions) into the
kernel at the same time just to make sure that at least one driver will suceed
in find it's mouse device. Nevertheless, only the inport and logitech busmouse
mouse drivers report with KERN_ERR log level if the mouse wasn't found. They
should use KERN_INFO instead, because it's not an error if the mouse isn't
attached at all.
Signed-off-by: Helge Deller <deller@gmx.de>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
|
| H A D | logibm.c | diff 2a0f9c4c452298da89b67060c7ca034ef7836aa9 Fri Nov 02 03:19:15 CET 2007 Helge Deller <deller@gmx.de> Input: inport, logibm - use KERN_INFO when reporting missing mouse
Many mouse drivers are often compiled (e.g. in Linux distributions) into the
kernel at the same time just to make sure that at least one driver will suceed
in find it's mouse device. Nevertheless, only the inport and logitech busmouse
mouse drivers report with KERN_ERR log level if the mouse wasn't found. They
should use KERN_INFO instead, because it's not an error if the mouse isn't
attached at all.
Signed-off-by: Helge Deller <deller@gmx.de>
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
|