From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: tree build failure
Date: Fri, 16 Jan 2009 08:25:49 +0100 [thread overview]
Message-ID: <1232090749.8870.85.camel@laptop> (raw)
In-Reply-To: <20090116163745.93f4e075.sfr@canb.auug.org.au>
On Fri, 2009-01-16 at 16:37 +1100, Stephen Rothwell wrote:
> Hi ,
>
> Today's linux-next build (powerpc allnoconfig) failed like this:
>
> In file included from kernel/sched.c:1703:
> kernel/sched_fair.c: In function 'adaptive_gran':
> kernel/sched_fair.c:1324: error: 'struct sched_entity' has no member named 'avg_wakeup'
>
> Caused by commit e52fb7c097238d34f4d8e2a596f8a3f85b0c0565
> ("sched: prefer wakers") from the sched tree.
>
> kernel/sched.c: In function 'enqueue_task':
> kernel/sched.c:1752: error: 'struct sched_entity' has no member named 'start_runtime'
> kernel/sched.c: In function 'dequeue_task':
> kernel/sched.c:1767: error: 'struct sched_entity' has no member named 'avg_wakeup'
> kernel/sched.c: In function 'try_to_wake_up':
> kernel/sched.c:2409: error: 'struct sched_entity' has no member named 'start_runtime'
> kernel/sched.c:2410: error: 'struct sched_entity' has no member named 'avg_wakeup'
> kernel/sched.c: In function '__sched_fork':
> kernel/sched.c:2454: error: 'struct sched_entity' has no member named 'start_runtime'
> kernel/sched.c:2455: error: 'struct sched_entity' has no member named 'avg_wakeup'
>
> Caused by commit 831451ac4e44d3a20b581ce726ef1d1144373f7d ("sched:
> introduce avg_wakeup") from the sched tree.
>
> These members depend on CONFIG_SCHEDSTATS.
That smells like a bad merge somewhere, I just checked -tip and it looks
like so:
struct sched_entity {
...
u64 avg_overlap;
u64 start_runtime;
u64 avg_wakeup;
u64 nr_migrations;
#ifdef CONFIG_SCHEDSTATS
u64 wait_start;
u64 wait_max;
...
};
next prev parent reply other threads:[~2009-01-16 7:26 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 5:37 linux-next: tree build failure Stephen Rothwell
2009-01-16 7:25 ` Peter Zijlstra [this message]
2009-01-16 9:03 ` Ingo Molnar
2009-01-16 10:39 ` Stephen Rothwell
2009-01-16 10:53 ` Ingo Molnar
2009-01-16 11:53 ` Stephen Rothwell
2009-01-16 12:32 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-12-16 7:21 Stephen Rothwell
2009-12-16 9:02 ` Felipe Balbi
2009-12-16 10:10 ` Liam Girdwood
2009-12-16 10:10 ` Liam Girdwood
2009-10-01 3:19 Stephen Rothwell
2009-10-01 7:58 ` Jens Axboe
2009-10-01 10:41 ` Stephen Rothwell
2009-09-29 9:28 Jan Beulich
2009-09-29 9:28 ` Jan Beulich
2009-09-29 9:28 ` Jan Beulich
2009-09-29 9:28 ` Jan Beulich
2009-09-29 9:51 ` roel kluin
2009-09-29 9:51 ` roel kluin
2009-09-29 9:51 ` roel kluin
2009-09-29 9:51 ` roel kluin
2009-09-30 6:29 ` Jan Beulich
2009-09-30 6:29 ` Jan Beulich
2009-09-30 6:29 ` Jan Beulich
2009-09-30 6:29 ` Jan Beulich
2009-09-29 23:39 ` Hollis Blanchard
2009-09-29 23:39 ` Hollis Blanchard
2009-09-29 23:39 ` Hollis Blanchard
2009-09-29 23:39 ` Hollis Blanchard
2009-09-30 6:35 ` Jan Beulich
2009-09-30 6:35 ` Jan Beulich
2009-09-30 6:35 ` Jan Beulich
2009-09-30 6:35 ` Jan Beulich
2009-10-02 15:48 ` Hollis Blanchard
2009-10-02 15:48 ` Hollis Blanchard
2009-10-02 15:48 ` Hollis Blanchard
2009-10-02 15:48 ` Hollis Blanchard
2009-10-05 6:58 ` Jan Beulich
2009-10-05 6:58 ` Jan Beulich
2009-10-05 6:58 ` Jan Beulich
2009-10-05 6:58 ` Jan Beulich
2009-10-09 19:14 ` Hollis Blanchard
2009-10-09 19:14 ` Hollis Blanchard
2009-10-09 19:14 ` Hollis Blanchard
2009-10-14 22:57 ` Hollis Blanchard
2009-10-14 22:57 ` Hollis Blanchard
2009-10-14 22:57 ` Hollis Blanchard
2009-10-15 7:27 ` Jan Beulich
2009-10-15 7:27 ` Jan Beulich
2009-10-15 7:27 ` Jan Beulich
2009-10-15 7:27 ` Jan Beulich
2009-10-19 18:19 ` Hollis Blanchard
2009-10-19 18:19 ` Hollis Blanchard
2009-10-19 18:19 ` Hollis Blanchard
2009-10-20 1:24 ` Rusty Russell
2009-10-20 1:12 ` Rusty Russell
2009-10-20 1:12 ` Rusty Russell
2009-10-20 1:29 ` Hollis Blanchard
2009-10-20 1:29 ` Hollis Blanchard
2009-10-20 1:29 ` Hollis Blanchard
2009-10-20 1:29 ` Hollis Blanchard
2009-09-24 5:21 Stephen Rothwell
2009-09-24 5:21 ` Stephen Rothwell
2009-09-24 5:21 ` Stephen Rothwell
2009-09-29 0:00 ` Hollis Blanchard
2009-09-29 0:00 ` Hollis Blanchard
2009-09-29 0:00 ` Hollis Blanchard
2009-09-29 0:00 ` Hollis Blanchard
2009-08-17 8:39 Stephen Rothwell
2009-08-03 0:35 Stephen Rothwell
2009-08-03 1:01 ` NeilBrown
2009-08-03 1:30 ` Stephen Rothwell
2009-07-27 7:53 Stephen Rothwell
2009-07-27 9:21 ` Karsten Keil
2009-07-27 15:06 ` David Miller
2009-07-28 4:22 ` Stephen Rothwell
2009-04-07 3:41 Stephen Rothwell
2009-04-07 10:00 ` Mark Brown
2009-04-08 1:48 ` Takashi Iwai
2009-03-23 9:38 Stephen Rothwell
2009-03-23 22:27 ` Mauro Carvalho Chehab
2009-03-23 23:25 ` Stephen Rothwell
2009-03-05 7:41 Stephen Rothwell
2009-03-06 5:01 ` Rusty Russell
2008-11-28 10:04 Stephen Rothwell
2008-11-28 10:25 ` Takashi Iwai
2008-11-28 10:43 ` Stephen Rothwell
2008-11-28 17:23 ` Takashi Iwai
2008-10-21 8:30 Stephen Rothwell
2008-08-25 10:33 Stephen Rothwell
2008-08-25 16:36 ` Steven Rostedt
2008-06-30 14:35 Stephen Rothwell
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=1232090749.8870.85.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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.