public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: akpm@osdl.org
Cc: linux-acpi@vger.kernel.org
Subject: Re: [patch 8/8] acpi-cpufreq: remove dead code
Date: Sat, 21 Oct 2006 01:28:06 -0400	[thread overview]
Message-ID: <200610210128.07621.len.brown@intel.com> (raw)
In-Reply-To: <200610202130.k9KLUUfN003257@shell0.pdx.osdl.net>

I would expect to see this same change in both speedstep-centrino.c and acpi-cpufreq.c, no?

On Friday 20 October 2006 17:30, akpm@osdl.org wrote:
> From: Andrew Morton <akpm@osdl.org>
> 
> arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c:396: warning: 'sw_any_bug_dmi_table' defined but not used
> 
> Cc: Len Brown <lenb@kernel.org>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
> ---
> 
>  arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c |    2 ++
>  1 files changed, 2 insertions(+)
> 
> diff -puN arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c~acpi-cpufreq-remove-dead-code arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
> --- a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c~acpi-cpufreq-remove-dead-code
> +++ a/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c
> @@ -402,6 +402,7 @@ static int sw_any_bug_found(struct dmi_s
>  	return 0;
>  }
>  
> +#ifdef CONFIG_SMP
>  static struct dmi_system_id sw_any_bug_dmi_table[] = {
>  	{
>  		.callback = sw_any_bug_found,
> @@ -414,6 +415,7 @@ static struct dmi_system_id sw_any_bug_d
>  	},
>  	{ }
>  };
> +#endif
>  
>  static int
>  acpi_cpufreq_cpu_init (
> _
> 

  reply	other threads:[~2006-10-21  5:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20 21:30 [patch 8/8] acpi-cpufreq: remove dead code akpm
2006-10-21  5:28 ` Len Brown [this message]
2006-10-21  5:31   ` Dave Jones

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=200610210128.07621.len.brown@intel.com \
    --to=len.brown@intel.com \
    --cc=akpm@osdl.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@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