From: Stephane Wirtel <stephane.wirtel@belgacom.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] 2.4.20-pre10-ac2 -- cpufreq
Date: Sat, 12 Oct 2002 10:43:36 +0200 [thread overview]
Message-ID: <20021012084336.GA7027@debian> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1220 bytes --]
cpufreq.c: In function `cpufreq_notify_transition':
cpufreq.c:941: `i' undeclared (first use in this function)
cpufreq.c:941: (Each undeclared identifier is reported only once
cpufreq.c:941: for each function it appears in.)
cpufreq.c: In function `cpufreq_restore':
cpufreq.c:1068: warning: statement with no effect
make[2]: *** [cpufreq.o] Error 1
make[2]: Leaving directory `/root/linux-2.4.19/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/root/linux-2.4.19/kernel'
make: *** [_dir_kernel] Error 2
you can add a 'int i'
stargate kernel # diff -urH cpufreq.c.old cpufreq.c
--- cpufreq.c.old 2002-10-07 21:17:09.000000000 +0200
+++ cpufreq.c 2002-10-07 21:17:27.000000000 +0200
@@ -927,6 +927,7 @@
*/
void cpufreq_notify_transition(struct cpufreq_freqs *freqs, unsigned
int state)
{
+ int i;
down(&cpufreq_notifier_sem);
switch (state) {
case CPUFREQ_PRECHANGE:
stargate kernel #
Best Regards
Stephane Wirtel
--
Stephane Wirtel <stephane.wirtel@belgacom.net>
LinuxMons : www.linux-mons.be
GPG ID : 1024D/C9C16DA7 | 5331 0B5B 21F0 0363 EACD B73E 3D11 E5BC C9C1 6DA7
[-- Attachment #1.2: cpufreq.patch --]
[-- Type: text/plain, Size: 298 bytes --]
--- cpufreq.c.old 2002-10-07 21:17:09.000000000 +0200
+++ cpufreq.c 2002-10-07 21:17:27.000000000 +0200
@@ -927,6 +927,7 @@
*/
void cpufreq_notify_transition(struct cpufreq_freqs *freqs, unsigned int state)
{
+ int i;
down(&cpufreq_notifier_sem);
switch (state) {
case CPUFREQ_PRECHANGE:
[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]
reply other threads:[~2002-10-12 8:38 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=20021012084336.GA7027@debian \
--to=stephane.wirtel@belgacom.net \
--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 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.