From: Thomas Schlichter <thomas.schlichter@web.de>
To: Andrew Morton <akpm@osdl.org>, Nick Piggin <piggin@cyberone.com.au>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.1-mm3
Date: Wed, 14 Jan 2004 20:11:44 +0100 [thread overview]
Message-ID: <200401142011.52301.thomas.schlichter@web.de> (raw)
In-Reply-To: <20040114014846.78e1a31b.akpm@osdl.org>
[-- Attachment #1.1: body text --]
[-- Type: text/plain, Size: 610 bytes --]
Hi,
the patch "sched-sibling-map-to-cpumask.patch" inroduced following compile
error on UP machines:
CC [M] arch/i386/kernel/cpu/cpufreq/p4-clockmod.o
arch/i386/kernel/cpu/cpufreq/p4-clockmod.c: In function `cpufreq_p4_setdc':
arch/i386/kernel/cpu/cpufreq/p4-clockmod.c:71: error: `cpu_sibling_map'
undeclared (first use in this function)
arch/i386/kernel/cpu/cpufreq/p4-clockmod.c:71: error: (Each undeclared
identifier is reported only once
arch/i386/kernel/cpu/cpufreq/p4-clockmod.c:71: error: for each function it
appears in.)
The attached patch fixes it...
Thomas Schlichter
[-- Attachment #1.2: fix_p4-clockmod.diff --]
[-- Type: text/x-diff, Size: 566 bytes --]
--- linux-2.6.1-mm3/arch/i386/kernel/cpu/cpufreq/p4-clockmod.c.orig 2004-01-14 18:15:05.891246656 +0100
+++ linux-2.6.1-mm3/arch/i386/kernel/cpu/cpufreq/p4-clockmod.c 2004-01-14 18:27:35.876231608 +0100
@@ -68,7 +68,11 @@
cpus_allowed = current->cpus_allowed;
/* only run on CPU to be set, or on its sibling */
+#ifdef CONFIG_SMP
affected_cpu_map = cpu_sibling_map[cpu];
+#else
+ affected_cpu_map = cpumask_of_cpu(cpu);
+#endif
set_cpus_allowed(current, affected_cpu_map);
BUG_ON(!cpu_isset(smp_processor_id(), affected_cpu_map));
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-14 19:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 9:48 2.6.1-mm3 Andrew Morton
2004-01-14 9:48 ` 2.6.1-mm3 Andrew Morton
2004-01-14 12:27 ` 2.6.1-mm3 Jes Sorensen
2004-01-14 12:27 ` 2.6.1-mm3 Jes Sorensen
2004-01-14 13:06 ` 2.6.1-mm3 Dmitry Torokhov
2004-01-14 13:06 ` 2.6.1-mm3 Dmitry Torokhov
2004-01-14 14:23 ` 2.6.1-mm3 sound oops Helge Hafting
2004-01-14 16:04 ` 2.6.1-mm3 (compile stats) John Cherry
2004-01-14 16:04 ` John Cherry
2004-01-14 19:11 ` Thomas Schlichter [this message]
2004-01-14 19:11 ` 2.6.1-mm3 Thomas Schlichter
2004-01-14 19:12 ` 2.6.1-mm3 Thomas Schlichter
2004-01-14 19:12 ` 2.6.1-mm3 Thomas Schlichter
2004-01-14 19:12 ` 2.6.1-mm3 Thomas Schlichter
2004-01-15 1:47 ` 2.6.1-mm3 Roberto Sanchez
2004-01-15 2:39 ` 2.6.1-mm3 Nick Piggin
2004-01-15 2:39 ` 2.6.1-mm3 Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2004-01-15 14:31 2.6.1-mm3 Andreas Jellinghaus
2004-01-15 23:01 ` 2.6.1-mm3 Greg KH
2004-01-16 10:04 ` 2.6.1-mm3 Andreas Jellinghaus
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=200401142011.52301.thomas.schlichter@web.de \
--to=thomas.schlichter@web.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
/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.