Distribution kernels are building cpufreq drivers into the kernel to get
faster boot; if the nForce2 driver is built in, then on systems that are
not supported by the driver (ie nearly all current systems), the message
cpufreq: No nForce2 chipset.
is printed at the KERN_ERR level, which means it goes to the console
even if quiet boot is turned on.
The best way to handle this is just to delete the message, since the
likelihood of it ever being of any use to anyone is very low, and other
cpufreq drivers don't print anything if no matching hardware is found.
Signed-off-by: Roland Dreier <rolandd@xxxxxxxxx>
---
arch/x86/kernel/cpu/cpufreq/cpufreq-nforce2.c | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/cpu/cpufreq/cpufreq-nforce2.c b/arch/x86/kernel/cpu/cpufreq/cpufreq-nforce2.c
index 965ea52..055fca3 100644
--- a/arch/x86/kernel/cpu/cpufreq/cpufreq-nforce2.c
+++ b/arch/x86/kernel/cpu/cpufreq/cpufreq-nforce2.c
@@ -419,10 +419,8 @@ static int __init nforce2_init(void)
/* TODO: do we need to detect the processor? */
/* detect chipset */
- if (nforce2_detect_chipset()) {
- printk(KERN_ERR "cpufreq: No nForce2 chipset.\n");
+ if (nforce2_detect_chipset())
return -ENODEV;
- }
return cpufreq_register_driver(&nforce2_driver);
}
--
To unsubscribe from this list: send the line "unsubscribe cpufreq" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
