summaryrefslogtreecommitdiffstats
path: root/drivers/leds
diff options
context:
space:
mode:
authorH Hartley Sweeten <hartleys@visionengravers.com>2010-01-06 15:34:55 -0700
committerRichard Purdie <rpurdie@linux.intel.com>2010-03-16 19:49:21 +0000
commitbb9b6ef70f08f256ab4b8ec127c17ee629b85350 (patch)
treece1abece2081cfffd14ef5ff3f479daf3481802b /drivers/leds
parent5e89a3484dea8a3d962f83fe497d064fbcde4e55 (diff)
downloadop-kernel-dev-bb9b6ef70f08f256ab4b8ec127c17ee629b85350.zip
op-kernel-dev-bb9b6ef70f08f256ab4b8ec127c17ee629b85350.tar.gz
leds: led-class.c - Quiet boot messages
As each led device gets registered a kernel message gets printed. In an embedded system with a number of leds this can produce a lot of output that just looks like noise. Change the message type to KERN_DEBUG since it might be useful in the dmesg output "after" booting. Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Diffstat (limited to 'drivers/leds')
-rw-r--r--drivers/leds/led-class.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
index 782f958..349e073 100644
--- a/drivers/leds/led-class.c
+++ b/drivers/leds/led-class.c
@@ -164,7 +164,7 @@ int led_classdev_register(struct device *parent, struct led_classdev *led_cdev)
led_trigger_set_default(led_cdev);
#endif
- printk(KERN_INFO "Registered led device: %s\n",
+ printk(KERN_DEBUG "Registered led device: %s\n",
led_cdev->name);
return 0;
OpenPOWER on IntegriCloud