From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Dave Jones <davej@redhat.com>
Cc: 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 19:23:30 +0100 [thread overview]
Message-ID: <20040214182330.GA5097@dominikbrodowski.de> (raw)
In-Reply-To: <20040214164142.GA29606@redhat.com>
On Sat, Feb 14, 2004 at 04:41:42PM +0000, Dave Jones wrote:
> I'd rather keep them multi-line in the source. It looks a lot more readable than just
> one line IMHO. I've no objection to killing off the \n's though.
As Pavel Machek told me, a single line warning is better, and KERN_DEBUG might
be missed if reading from /var/log/messages. As Dave Jones told me, multi-line
printk's are more readable, though.
arch/i386/kernel/cpu/cpufreq/p4-clockmod.c | 17 ++++++++++-------
1 files changed, 10 insertions(+), 7 deletions(-)
Dominik
diff -ruN linux-original/arch/i386/kernel/cpu/cpufreq/p4-clockmod.c linux/arch/i386/kernel/cpu/cpufreq/p4-clockmod.c
--- linux-original/arch/i386/kernel/cpu/cpufreq/p4-clockmod.c 2004-02-14 19:22:23.907928496 +0100
+++ linux/arch/i386/kernel/cpu/cpufreq/p4-clockmod.c 2004-02-14 19:18:37.167398296 +0100
@@ -181,21 +181,24 @@
{
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");
return speedstep_get_processor_frequency(SPEEDSTEP_PROCESSOR_PM);
}
if (c->x86 != 0xF) {
- printk(KERN_DEBUG PFX "Unknown p4-clockmod-capable CPU. Please send an e-mail to <linux@brodo.de>\n");
+ printk(KERN_WARNING PFX "Unknown p4-clockmod-capable CPU. Please send an e-mail to <linux@brodo.de>\n");
return 0;
}
if (speedstep_detect_processor() == SPEEDSTEP_PROCESSOR_P4M) {
- printk(KERN_DEBUG PFX "Warning: Pentium 4-M detected. The speedstep-ich or acpi cpufreq \n");
- printk(KERN_DEBUG PFX "modules offers voltage scaling in addition of frequency scaling. You\n");
- printk(KERN_DEBUG PFX "should use either one instead of p4-clockmod, if possible.\n");
+ printk(KERN_WARNING PFX "Warning: Pentium 4-M detected. ");
+ printk("The speedstep-ich or acpi cpufreq modules offers ");
+ printk("voltage scaling in addition of frequency scaling. ");
+ printk("You should use either one instead of p4-clockmod, ");
+ printk("if possible.\n");
return speedstep_get_processor_frequency(SPEEDSTEP_PROCESSOR_P4M);
}
next prev parent reply other threads:[~2004-02-14 18:23 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 [this message]
2004-02-14 18:29 ` Russell King
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=20040214182330.GA5097@dominikbrodowski.de \
--to=linux@dominikbrodowski.de \
--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.