Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932422Ab0AFWeb (ORCPT ); Wed, 6 Jan 2010 17:34:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932327Ab0AFWea (ORCPT ); Wed, 6 Jan 2010 17:34:30 -0500 Received: from [206.15.93.42] ([206.15.93.42]:14606 "EHLO visionfs1.visionengravers.com" rhost-flags-FAIL-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S932264Ab0AFWe3 (ORCPT ); Wed, 6 Jan 2010 17:34:29 -0500 From: H Hartley Sweeten To: Linux Kernel Subject: [PATCH] led-class.c: quiet boot messages Date: Wed, 6 Jan 2010 15:34:55 -0700 Cc: rpurdie@rpsys.net MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201001061534.55707.hartleys@visionengravers.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1101 Lines: 32 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 Cc: Richard Purdie --- 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; -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/