From: Russell King <rmk@arm.linux.org.uk>
To: Dave Jones <davej@redhat.com>, cpufreq@www.linux.org.uk
Subject: Re: [PATCH >=2.6.4] single-line, but KERN_WARNING message in p4-clockmod
Date: Sat, 14 Feb 2004 18:29:50 +0000 [thread overview]
Message-ID: <20040214182950.C16829@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040214182330.GA5097@dominikbrodowski.de>; from linux@dominikbrodowski.de on Sat, Feb 14, 2004 at 07:23:30PM +0100
On Sat, Feb 14, 2004 at 07:23:30PM +0100, Dominik Brodowski wrote:
> if ((c->x86 == 0x06) && (c->x86_model == 0x09)) {
> /* Pentium M */
> - printk(KERN_DEBUG PFX "Warning: Pentium M detected. The speedstep_centrino module\n");
> - printk(KERN_DEBUG PFX "offers voltage scaling in addition of frequency scaling. You\n");
> - printk(KERN_DEBUG PFX "should use that instead of p4-clockmod, if possible.\n");
> + printk(KERN_WARNING PFX "Warning: Pentium M detected. ");
> + printk("The speedstep_centrino module offers voltage scaling");
> + printk(" in addition of frequency scaling. You should use ");
> + printk("that instead of p4-clockmod, if possible.\n");
I think that's a lot worse for one major reason - you loose the atomicity
of printk() if you do that, especially if you use serial console.
I haven't seen this done anywhere else in the kernel... lets not start
doing it now.
printk(KERN_WARNING PFX "Warning: Pentium M detected. "
"The speedstep_centrino module offers voltage scaling "
"in addition of frequency scaling. You should use "
"that instead of p4-clockmod, if possible.\n");
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-02-14 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 16:01 [PATCH >=2.6.4] single-line, but KERN_WARNING message in p4-clockmod Dominik Brodowski
2004-02-14 16:41 ` Dave Jones
2004-02-14 18:23 ` Dominik Brodowski
2004-02-14 18:29 ` Russell King [this message]
2004-02-14 18:45 ` Dominik Brodowski
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=20040214182950.C16829@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.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.