All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarod Wilson <jarod@redhat.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: davej@redhat.com, cpufreq@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: Remove KERN_ERR output if nForce2 chipset not found
Date: Fri, 6 Mar 2009 16:06:04 -0500	[thread overview]
Message-ID: <200903061606.05975.jarod@redhat.com> (raw)
In-Reply-To: <ada3adqid5v.fsf@cisco.com>

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@cisco.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@redhat.com

  reply	other threads:[~2009-03-06 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06 20:55 [PATCH] cpufreq: Remove KERN_ERR output if nForce2 chipset not found Roland Dreier
2009-03-06 21:06 ` Jarod Wilson [this message]
2009-03-06 21:51   ` Roland Dreier
2009-03-06 22:01     ` Jarod Wilson

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=200903061606.05975.jarod@redhat.com \
    --to=jarod@redhat.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdreier@cisco.com \
    /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.