All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Thomas Renninger <trenn@suse.de>
Cc: davej@redhat.com, sfr@canb.auug.org.au,
	linux-next@vger.kernel.org, cpufreq@vger.kernel.org
Subject: Re: [PATCH 1/2] CPUFREQ: powernow-k8: Forgot to use printk instead of WARN_ONCE in last patch
Date: Thu, 5 Feb 2009 13:02:03 +0100	[thread overview]
Message-ID: <20090205120203.GA8799@elte.hu> (raw)
In-Reply-To: <1233829109-23358-2-git-send-email-trenn@suse.de>


* Thomas Renninger <trenn@suse.de> wrote:

> Signed-off-by: Thomas Renninger <trenn@suse.de>
> ---
>  arch/x86/kernel/cpu/cpufreq/powernow-k8.c |   12 ++++++------
>  1 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/arch/x86/kernel/cpu/cpufreq/powernow-k8.c b/arch/x86/kernel/cpu/cpufreq/powernow-k8.c
> index 83515f1..5aa832f 100644
> --- a/arch/x86/kernel/cpu/cpufreq/powernow-k8.c
> +++ b/arch/x86/kernel/cpu/cpufreq/powernow-k8.c
> @@ -1247,12 +1247,12 @@ static int __cpuinit powernowk8_cpu_init(struct cpufreq_policy *pol)
>  			 * thing gets introduced
>  			 */
>  			if (!print_once) {
> -				WARN_ONCE(1, KERN_ERR FW_BUG PFX "Your BIOS "
> -					  "does not provide ACPI _PSS objects "
> -					  "in a way that Linux understands. "
> -					  "Please report this to the Linux ACPI"
> -					  " maintainers and complain to your "
> -					  "BIOS vendor.\n");
> +				printk(KERN_ERR FW_BUG PFX "Your BIOS "
> +				       "does not provide ACPI _PSS objects "
> +				       "in a way that Linux understands. "
> +				       "Please report this to the Linux ACPI"
> +				       " maintainers and complain to your "
> +				       "BIOS vendor.\n");
>  				print_once++;

hm, why the open-coded WARN_ONCE? (which print_once flag + the printk in 
essence is)

So please use WARN_ONCE(), and indent it all one tab to the left which will 
solve at least part of that ugly 6-line split up thing. And if it's a 
WARN_ONCE() then kerneloops.org will pick it up too.

	Ingo

  reply	other threads:[~2009-02-05 12:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-05 10:18 On top fixes for my last patches Thomas Renninger
2009-02-05 10:18 ` [PATCH 1/2] CPUFREQ: powernow-k8: Forgot to use printk instead of WARN_ONCE in last patch Thomas Renninger
2009-02-05 12:02   ` Ingo Molnar [this message]
2009-02-05 12:09     ` Thomas Renninger
2009-02-05 12:33       ` Ingo Molnar
2009-02-05 12:53         ` Thomas Renninger
2009-02-05 13:26           ` Ingo Molnar
2009-02-05 12:27     ` Thomas Renninger
2009-02-05 12:42       ` Ingo Molnar
2009-02-05 13:04         ` [tip:core/printk] printk: introduce printk_once() Ingo Molnar
2009-02-05 14:12           ` Thomas Renninger
2009-02-05 10:18 ` [PATCH 2/2] CPUFREQ: Use static or it won't compile if conservative and ondemand are set =y Thomas Renninger

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=20090205120203.GA8799@elte.hu \
    --to=mingo@elte.hu \
    --cc=cpufreq@vger.kernel.org \
    --cc=davej@redhat.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=trenn@suse.de \
    /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.