public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Greg KH <gregkh@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] Driver core: Reduce the level of request_firmware() messages
Date: Sat, 27 Feb 2010 21:43:22 +0100	[thread overview]
Message-ID: <201002272143.22156.rjw@sisk.pl> (raw)

From: Rafael J. Wysocki <rjw@sisk.pl>

The messages from _request_firmware() informing that firmware is
being requested or built-in firmware is going to be used are printed
at KERN_INFO, which produces lots of noise on systems with huge
numbers of AMD CPUs.  Reduce the level of these messages to
KERN_DEBUG to get rid of that noise.

Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
---
 drivers/base/firmware_class.c |    5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

Index: linux-2.6.32-SLE11-SP1/drivers/base/firmware_class.c
===================================================================
--- linux-2.6.32-SLE11-SP1.orig/drivers/base/firmware_class.c
+++ linux-2.6.32-SLE11-SP1/drivers/base/firmware_class.c
@@ -487,15 +487,14 @@ _request_firmware(const struct firmware 
 	     builtin++) {
 		if (strcmp(name, builtin->name))
 			continue;
-		dev_info(device, "firmware: using built-in firmware %s\n",
-			 name);
+		dev_dbg(device, "firmware: using built-in firmware %s\n", name);
 		firmware->size = builtin->size;
 		firmware->data = builtin->data;
 		return 0;
 	}
 
 	if (uevent)
-		dev_info(device, "firmware: requesting %s\n", name);
+		dev_dbg(device, "firmware: requesting %s\n", name);
 
 	retval = fw_setup_device(firmware, &f_dev, name, device, uevent);
 	if (retval)

             reply	other threads:[~2010-02-27 20:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-27 20:43 Rafael J. Wysocki [this message]
2010-02-28  3:13 ` [PATCH] Driver core: Reduce the level of request_firmware() messages Greg KH
2010-02-28  4:43 ` Jaswinder Singh Rajput
2010-02-28 12:13   ` Rafael J. Wysocki
2010-02-28 16:33     ` Jaswinder Singh Rajput
2010-02-28 19:54       ` Rafael J. Wysocki
2010-02-28 20:13         ` Jaswinder Singh Rajput
2010-03-15 20:16           ` Greg KH
2010-03-15 21:27             ` Rafael J. Wysocki
2010-03-15 23:34               ` Jaswinder Singh Rajput
2010-03-15 23:40                 ` Rafael J. Wysocki
2010-03-15 23:55                   ` Jaswinder Singh Rajput
2010-03-15 23:44                 ` Greg KH
2010-03-16  0:17                   ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201002272143.22156.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox