From: Nigel Cunningham <ncunningham@cyclades.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>,
Linux-pm mailing list <linux-pm@lists.osdl.org>
Subject: [PATCH] Address BUG: using smp_processor_id() in preemptible [00000001] code
Date: Fri, 22 Jul 2005 13:59:01 +1000 [thread overview]
Message-ID: <1122004741.3033.49.camel@localhost> (raw)
This patch fixes a warning in the disable_nonboot_cpus call in
kernel/power/smp.c.
Please apply.
Signed-off by: Nigel Cunningham <nigel@suspend2.net>
smp.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -ruNp 830-smp_processor_id_warning.patch-old/kernel/power/smp.c 830-smp_processor_id_warning.patch-new/kernel/power/smp.c
--- 830-smp_processor_id_warning.patch-old/kernel/power/smp.c 2005-07-18 06:37:08.000000000 +1000
+++ 830-smp_processor_id_warning.patch-new/kernel/power/smp.c 2005-07-22 11:09:16.000000000 +1000
@@ -38,7 +38,7 @@ void disable_nonboot_cpus(void)
}
printk("Error taking cpu %d down: %d\n", cpu, error);
}
- BUG_ON(smp_processor_id() != 0);
+ BUG_ON(raw_smp_processor_id() != 0);
if (error)
panic("cpus not sleeping");
}
--
Evolution.
Enumerate the requirements.
Consider the interdependencies.
Calculate the probabilities.
reply other threads:[~2005-07-22 4:23 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=1122004741.3033.49.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
/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