From: Adrian Bunk <bunk@stusta.de>
To: davej@codemonkey.org.uk
Cc: cpufreq@lists.linux.org.uk, linux-kernel@vger.kernel.org
Subject: [2.6 patch] drivers/cpufreq/cpufreq.c: fix a compile warning with SMP=n
Date: Mon, 7 Nov 2005 21:03:45 +0100 [thread overview]
Message-ID: <20051107200345.GJ3847@stusta.de> (raw)
This patch fixes the following compile warning with CONFIG_SMP=n:
<-- snip -->
...
CC drivers/cpufreq/cpufreq.o
drivers/cpufreq/cpufreq.c: In function 'cpufreq_remove_dev':
drivers/cpufreq/cpufreq.c:696: warning: unused variable 'cpu_sys_dev'
...
<-- snip -->
Signed-off-by: Adrian Bunk <bunk@stusta.de>
--- linux-2.6.14-mm1-full/drivers/cpufreq/cpufreq.c.old 2005-11-07 19:27:33.000000000 +0100
+++ linux-2.6.14-mm1-full/drivers/cpufreq/cpufreq.c 2005-11-07 19:27:50.000000000 +0100
@@ -693,8 +693,8 @@
unsigned int cpu = sys_dev->id;
unsigned long flags;
struct cpufreq_policy *data;
- struct sys_device *cpu_sys_dev;
#ifdef CONFIG_SMP
+ struct sys_device *cpu_sys_dev;
unsigned int j;
#endif
reply other threads:[~2005-11-07 20:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20051107200345.GJ3847@stusta.de \
--to=bunk@stusta.de \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--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