From: Roland Dreier <rdreier@cisco.com>
To: Jarod Wilson <jarod@redhat.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, 06 Mar 2009 13:51:49 -0800 [thread overview]
Message-ID: <adaljrigw0a.fsf@cisco.com> (raw)
In-Reply-To: <200903061606.05975.jarod@redhat.com> (Jarod Wilson's message of "Fri, 6 Mar 2009 16:06:04 -0500")
> 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.
Sorry, missed that. I considered the demotion to KERN_INFO but a) no
other cpufreq drivers seem to print anything if the device isn't found
and b) I can't imagine a realistic case of when the message would *ever*
be useful.
- R.
next prev parent reply other threads:[~2009-03-06 21:52 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
2009-03-06 21:51 ` Roland Dreier [this message]
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=adaljrigw0a.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=cpufreq@vger.kernel.org \
--cc=davej@redhat.com \
--cc=jarod@redhat.com \
--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