public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Rick Lindsley <ricklind@us.ibm.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc3-mm1: SCHEDSTATS compile error
Date: Thu, 5 Aug 2004 22:20:16 +0200	[thread overview]
Message-ID: <20040805202016.GP2746@fs.tum.de> (raw)
In-Reply-To: <200408051915.i75JFN616956@owlet.beaverton.ibm.com>

On Thu, Aug 05, 2004 at 12:15:23PM -0700, Rick Lindsley wrote:
>     > This looks like it could happen if you compile without CONFIG_SMP ...
>     > which admittedly I have not tried since the sched-domain code was
>     > introduced.  Adrian, was this the situation in your case?
>     
>     Yes.
> 
> Ok.  Please try this patch (applied to rc3-mm1).

Thanks, it fixes compilation for me.

> Rick

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  parent reply	other threads:[~2004-08-05 20:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 10:19 2.6.8-rc3-mm1 Andrew Morton
2004-08-05 11:18 ` 2.6.8-rc3-mm1: SCHEDSTATS compile error Adrian Bunk
2004-08-05 15:25   ` Martin J. Bligh
2004-08-05 16:49     ` Adrian Bunk
2004-08-05 18:17       ` Rick Lindsley
2004-08-05 18:20         ` Adrian Bunk
2004-08-05 19:15           ` Rick Lindsley
2004-08-05 19:54             ` Luiz Fernando N. Capitulino
2004-08-05 20:20             ` Adrian Bunk [this message]
2004-08-09 19:46         ` Bill Davidsen
2004-08-09 19:51           ` Rick Lindsley
2004-08-05 11:20 ` 2.6.8-rc3-mm1 Sean Neakums
2004-08-05 11:49 ` 2.6.8-rc3-mm1: ALSA: vortex_asXtalkGainsAllChan multiple definitions Adrian Bunk
2004-08-05 12:38 ` 2.6.8-rc3-mm1: ip2mainc-add-missing-pci_enable_device breaks compilation Adrian Bunk
2004-08-05 15:45   ` Bjorn Helgaas
2004-08-05 12:50 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 13:03 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 21:38   ` 2.6.8-rc3-mm1 Andrew Morton
2004-08-06 15:25     ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 13:24 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 13:36 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 16:13 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 16:42 ` 2.6.8-rc3-mm1 Christoph Hellwig
2004-08-05 20:24   ` 2.6.8-rc3-mm1 Alan Cox
2004-08-05 16:52 ` 2.6.8-rc3-mm1 (compile stats) John Cherry
2004-08-06  3:34 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-06  4:24   ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-06  4:39     ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-06  5:17       ` 2.6.8-rc3-mm1 Andrew Morton
     [not found] ` <20040806075219.GW17188@holomorphy.com>
2004-08-06  8:11   ` alpha signal race fixes William Lee Irwin III
2004-08-06 12:48 ` 2.6.8-rc3-mm1 Mark Watts
2004-08-06 19:58 ` 2.6.8-rc3-mm1: sk98lin/skge.c compile error with PROC_FS=n Adrian Bunk
2004-08-06 19:58 ` 2.6.8-rc3-mm1: PROC_FS=n link errors Adrian Bunk
2004-08-06 20:24   ` William Lee Irwin III
2004-08-06 20:33     ` 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=20040805202016.GP2746@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=ricklind@us.ibm.com \
    /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