summaryrefslogtreecommitdiff
path: root/drivers/input/mouse/logibm.c
diff options
context:
space:
mode:
authorHelge Deller <deller@gmx.de>2007-11-02 05:19:15 +0300
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2007-11-02 05:19:15 +0300
commit2a0f9c4c452298da89b67060c7ca034ef7836aa9 (patch)
treed8317d0c410abc0ccb725ae734c2e6201add2ca5 /drivers/input/mouse/logibm.c
parent2a3e480d4b3392ce8907089094bd074575f9bb2a (diff)
downloadlinux-2a0f9c4c452298da89b67060c7ca034ef7836aa9.tar.xz
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>
Diffstat (limited to 'drivers/input/mouse/logibm.c')
-rw-r--r--drivers/input/mouse/logibm.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/input/mouse/logibm.c b/drivers/input/mouse/logibm.c
index b23a4f3ea5cd..37e7c75b43bd 100644
--- a/drivers/input/mouse/logibm.c
+++ b/drivers/input/mouse/logibm.c
@@ -134,7 +134,7 @@ static int __init logibm_init(void)
udelay(100);
if (inb(LOGIBM_SIGNATURE_PORT) != LOGIBM_SIGNATURE_BYTE) {
- printk(KERN_ERR "logibm.c: Didn't find Logitech busmouse at %#x\n", LOGIBM_BASE);
+ printk(KERN_INFO "logibm.c: Didn't find Logitech busmouse at %#x\n", LOGIBM_BASE);
err = -ENODEV;
goto err_release_region;
}