linux-kernel - Re: [PATCH] cpufreq: Remove KERN_ERR output if nForce2 chipset not found

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 6 Mar 2009 16:06:04 -0500
From:	Jarod Wilson <jarod@...hat.com>
To:	Roland Dreier <rdreier@...co.com>
Cc:	davej@...hat.com, cpufreq@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpufreq: Remove KERN_ERR output if nForce2 chipset not found

On Friday 06 March 2009 15:55:56 Roland Dreier wrote:
> 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@...co.com>

Nb: Matthew Garrett submitted a similar-but-different patch a week or
two ago on the cpufreq list that demoted the message to KERN_INFO.

-- 
Jarod Wilson
jarod@...hat.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/