From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Cc: Arjan van de Ven <arjan@infradead.org>
Subject: [PATCH] quiet MMCONFIG related printks
Date: Mon, 1 Jan 2007 21:01:38 -0800 [thread overview]
Message-ID: <200701012101.38427.jbarnes@virtuousgeek.org> (raw)
Using MMCONFIG for PCI config space access is simply an optimization, not
a requirement. Therefore, when it can't be used, there's no need for
KERN_ERR level message. This patch makes the message a KERN_INFO instead
to reduce some of the noise in a kernel boot with the 'quiet' option.
(Note that this has no effect on a normal boot, which is ridiculously
verbose these days.)
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Thanks,
Jesse
diff --git a/arch/i386/pci/mmconfig.c b/arch/i386/pci/mmconfig.c
index e2616a2..b95e7f3 100644
--- a/arch/i386/pci/mmconfig.c
+++ b/arch/i386/pci/mmconfig.c
@@ -210,9 +210,9 @@ void __init pci_mmcfg_init(int type)
if (type == 1 && !e820_all_mapped(pci_mmcfg_config[0].base_address,
pci_mmcfg_config[0].base_address + MMCONFIG_APER_MIN,
E820_RESERVED)) {
- printk(KERN_ERR "PCI: BIOS Bug: MCFG area at %x is not E820-reserved\n",
+ printk(KERN_INFO "PCI: BIOS Bug: MCFG area at %x is not E820-reserved\n",
pci_mmcfg_config[0].base_address);
- printk(KERN_ERR "PCI: Not using MMCONFIG.\n");
+ printk(KERN_INFO "PCI: Not using MMCONFIG.\n");
return;
}
next reply other threads:[~2007-01-02 5:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 5:01 Jesse Barnes [this message]
2007-01-02 10:36 ` [PATCH] quiet MMCONFIG related printks Alan
2007-01-02 16:37 ` Jesse Barnes
2007-01-03 13:52 ` Arjan van de Ven
2007-01-03 13:53 ` Arjan van de Ven
2007-01-03 16:49 ` Jesse Barnes
2007-01-03 17:01 ` Arjan van de Ven
2007-01-03 19:29 ` Stephen Clark
2007-01-03 17:20 ` Jesse Barnes
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=200701012101.38427.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.