mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-rc3-mm1 problems (ACPI and others)
Date: Thu, 10 Jun 2004 22:47:39 +0200	[thread overview]
Message-ID: <16584.51435.861827.302250@alkaid.it.uu.se> (raw)
In-Reply-To: <Pine.LNX.4.58.0406102131360.18039@alpha.polcom.net>

Grzegorz Kulewski writes:
 > Hi,
 > 
 > I have the following problems with 2.6.7-rc3-mm1:
...
 > 3. PERFCTR gives me compile time errors (see compiler messages). Do I need 
 > any special patches?
...
 >   CC      drivers/perfctr/x86.o
 > /usr/src/linux-2.6.7-rc3-mm1/drivers/perfctr/x86.c: In function 
 > `finalise_backpatching':
 > /usr/src/linux-2.6.7-rc3-mm1/drivers/perfctr/x86.c:1137: error: syntax 
 > error before '{' token

Perfctr is the victim of broken cpumask patches.
Apply the patch below.

diff -ruN linux-2.6.7-rc3-mm1/include/linux/cpumask.h linux-2.6.7-rc3-mm1.cpu_mask_none-fix/include/linux/cpumask.h
--- linux-2.6.7-rc3-mm1/include/linux/cpumask.h	2004-06-09 19:38:39.000000000 +0200
+++ linux-2.6.7-rc3-mm1.cpu_mask_none-fix/include/linux/cpumask.h	2004-06-09 22:01:28.470416000 +0200
@@ -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)
 

  reply	other threads:[~2004-06-10 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10 20:45 [PATCH]Re:2.6.7-rc3-mm1 long
2004-06-10 19:57 ` 2.6.7-rc3-mm1 problems (ACPI and others) Grzegorz Kulewski
2004-06-10 20:47   ` Mikael Pettersson [this message]
2004-06-10 23:10   ` Pozsar Balazs
2004-06-11  1:05 ` [PATCH]Re:2.6.7-rc3-mm1 William Lee Irwin III

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=16584.51435.861827.302250@alkaid.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=akpm@osdl.org \
    --cc=kangur@polcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®