From: William Lee Irwin III <wli@holomorphy.com>
To: Clemens Schwaighofer <cs@tequila.co.jp>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc3-mm1
Date: Wed, 9 Jun 2004 22:31:34 -0700 [thread overview]
Message-ID: <20040610053134.GV1444@holomorphy.com> (raw)
In-Reply-To: <40C7EE96.4020206@tequila.co.jp>
On Thu, Jun 10, 2004 at 02:16:06PM +0900, Clemens Schwaighofer wrote:
> compile error in:
> drivers/perfctr/x86.c: In function `finalise_backpatching':
> drivers/perfctr/x86.c:1137: error: parse error before '{' token
> make[2]: *** [drivers/perfctr/x86.o] Error 1
> make[1]: *** [drivers/perfctr] Error 2
> make: *** [drivers] Error 2
> the kernel compiled fine with 2.6.7-rc2-mm2.
> config attached.
You will likely need other fixes, but...
Index: mm1-2.6.7-rc3/include/linux/cpumask.h
===================================================================
--- mm1-2.6.7-rc3.orig/include/linux/cpumask.h 2004-06-09 08:06:54.000000000 -0700
+++ mm1-2.6.7-rc3/include/linux/cpumask.h 2004-06-09 22:30:18.000000000 -0700
@@ -248,9 +248,9 @@
#endif
#define CPU_MASK_NONE \
-{ { \
+((cpumask_t) { { \
[0 ... BITS_TO_LONGS(NR_CPUS)-1] = 0UL \
-} }
+} })
#define cpus_addr(src) ((src).bits)
next prev parent reply other threads:[~2004-06-10 5:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 8:50 2.6.7-rc3-mm1 Andrew Morton
2004-06-09 11:25 ` 2.6.7-rc3-mm1 Eric BEGOT
2004-06-09 13:13 ` 2.6.7-rc3-mm1 Zwane Mwaikambo
2004-06-09 13:36 ` 2.6.7-rc3-mm1 William Lee Irwin III
2004-06-09 13:42 ` 2.6.7-rc3-mm1 William Lee Irwin III
2004-06-09 13:43 ` 2.6.7-rc3-mm1 Zwane Mwaikambo
2004-06-09 14:48 ` 2.6.7-rc3-mm1 William Lee Irwin III
2004-06-09 14:58 ` 2.6.7-rc3-mm1 William Lee Irwin III
2004-06-09 15:16 ` 2.6.7-rc3-mm1 William Lee Irwin III
[not found] ` <40C73198.4080700@yahoo.fr>
2004-06-09 15:50 ` 2.6.7-rc3-mm1 William Lee Irwin III
2004-06-09 16:35 ` 2.6.7-rc3-mm1 Norberto Bensa
2004-06-09 17:05 ` 2.6.7-rc3-mm1 William Lee Irwin III
2004-06-09 17:46 ` 2.6.7-rc3-mm1 Norberto Bensa
2004-06-10 3:38 ` 2.6.7-rc3-mm1 Norberto Bensa
2004-06-09 17:59 ` 2.6.7-rc3-mm1 William Lee Irwin III
2004-06-09 19:50 ` 2.6.7-rc3-mm1 William Lee Irwin III
2004-06-09 23:44 ` 2.6.7-rc3-mm1 (compile stats) John Cherry
2004-06-10 2:10 ` 2.6.7-rc3-mm1 Phil Brunner
2004-06-10 2:22 ` 2.6.7-rc3-mm1 Andrew Morton
2004-06-10 2:52 ` 2.6.7-rc3-mm1 William Lee Irwin III
2004-06-10 8:59 ` 2.6.7-rc3-mm1 Phil Brunner
2004-06-10 5:16 ` 2.6.7-rc3-mm1 Clemens Schwaighofer
2004-06-10 5:31 ` William Lee Irwin III [this message]
2004-06-10 6:54 ` 2.6.7-rc3-mm1 Clemens Schwaighofer
2004-06-11 4:36 ` 2.6.7-rc3-mm1 Paul Jackson
2004-06-11 5:47 ` 2.6.7-rc3-mm1 Andrew Morton
2004-06-11 5:53 ` 2.6.7-rc3-mm1 Paul Jackson
-- strict thread matches above, loose matches on Subject: below --
2004-06-09 15:33 2.6.7-rc3-mm1 Peter Maas
2004-06-09 15:52 ` 2.6.7-rc3-mm1 William Lee Irwin III
2004-06-09 20:03 2.6.7-rc3-mm1 Nguyen, Tom L
2004-06-10 0:51 2.6.7-rc3-mm1 Nguyen, Tom L
[not found] <2576k-4hW-13@gated-at.bofh.it>
[not found] ` <25LZK-88C-17@gated-at.bofh.it>
2004-06-11 10:48 ` 2.6.7-rc3-mm1 Andi Kleen
2004-06-11 11:32 ` 2.6.7-rc3-mm1 Paul Jackson
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=20040610053134.GV1444@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=cs@tequila.co.jp \
--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