From: Gregory Haskins <ghaskins@novell.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] RT scheduler updates for tip
Date: Mon, 12 Jan 2009 10:05:16 -0500 [thread overview]
Message-ID: <496B5C2C.2050908@novell.com> (raw)
In-Reply-To: <20090112144548.GA14016@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
Ingo Molnar wrote:
> * Gregory Haskins <ghaskins@novell.com> wrote:
>
>
>> Ingo Molnar wrote:
>>
>>> * Ingo Molnar <mingo@elte.hu> wrote:
>>>
>>>
>>>
>>>>> Hi Ingo,
>>>>> I have rebased the series against tip/cpus4096 as of today. I
>>>>> built/boot this kernel for both SMP/UP on a 4-way x86_64 box, and they
>>>>> look sane. Let me know if they still look broken to you.
>>>>>
>>>>>
>>> yes, i still get build failures:
>>>
>>> kernel/sched_rt.c:574: error: 'struct rq' has no member named 'cpu'
>>> kernel/sched_rt.c:619: error: 'rq' undeclared (first use in this function)
>>> kernel/sched_rt.c:619: error: (Each undeclared identifier is reported only once
>>> kernel/sched_rt.c:619: error: for each function it appears in.)
>>> kernel/sched_rt.c:667: error: 'rq' undeclared (first use in this function)
>>>
>>> so i've excluded tip/sched/rt from tip/master for now.
>>>
>>> Ingo
>>>
>>>
>> Hey Ingo,
>> Sorry for all these problems. I am not sure what is happening since
>> it seems to build fine for me on this end.
>>
>> I just pulled down tip/sched/rt (sha
>> 0a6d4e1dc9154c4376358663d74060d1e33d203e) and built for my x86_64
>> machine with both SMP and UP (configs attached). They both completed
>> without errors. Could you send me the config you are having trouble
>> with?
>>
>
> dont have it anymore - but you can look at the build error itself and
> figure out what config options it needs to trigger such problems
Yes, of course. At least one of us has engaged their brains this AM ;)
Thanks. Fix forthcoming.
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-01-12 15:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 14:24 [git pull] RT scheduler updates for tip Gregory Haskins
2008-12-08 14:32 ` Ingo Molnar
2008-12-08 16:05 ` [PATCH] sched: fix build failure in kernel/sched_rt.c Ingo Molnar
2008-12-08 16:14 ` Gregory Haskins
2008-12-08 16:12 ` [git pull] RT scheduler updates for tip Ingo Molnar
2008-12-08 16:57 ` Gregory Haskins
2008-12-09 14:35 ` Gregory Haskins
2008-12-12 11:34 ` Ingo Molnar
2008-12-12 11:49 ` Ingo Molnar
2008-12-29 15:37 ` Gregory Haskins
2008-12-29 18:13 ` Gregory Haskins
2009-01-11 4:01 ` Ingo Molnar
2009-01-11 9:53 ` Ingo Molnar
2009-01-12 14:45 ` Gregory Haskins
2009-01-12 14:45 ` Ingo Molnar
2009-01-12 15:05 ` Gregory Haskins [this message]
2009-01-12 19:23 ` [git pull] fixes for tip/sched/rt Gregory Haskins
2009-01-13 1:43 ` Ingo Molnar
2009-01-13 2:37 ` [PATCH v2] sched: fix build error in kernel/sched_rt.c when RT_GROUP_SCHED && !SMP Gregory Haskins
2009-01-14 8:01 ` Ingo Molnar
2009-01-14 10:54 ` Peter Zijlstra
2009-01-14 11:03 ` Ingo Molnar
2009-01-14 13:21 ` Gregory Haskins
2009-01-14 14:46 ` [PATCH v3 0/2] fixes for tip/sched/rt Gregory Haskins
2009-01-14 14:46 ` [PATCH v3 1/2] sched: de CPP-ify the scheduler code Gregory Haskins
2009-01-14 15:11 ` Steven Rostedt
2009-01-14 15:28 ` Gregory Haskins
2009-01-14 14:46 ` [PATCH v3 2/2] sched: fix build error in kernel/sched_rt.c when RT_GROUP_SCHED && !SMP Gregory Haskins
2009-01-15 12:30 ` [PATCH v3 0/2] fixes for tip/sched/rt Ingo Molnar
2009-01-16 13:35 ` Ingo Molnar
2009-01-16 13:45 ` Gregory Haskins
2009-01-16 13:46 ` Peter Zijlstra
2009-01-16 14:02 ` Gregory Haskins
2009-01-16 14:02 ` Ingo Molnar
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=496B5C2C.2050908@novell.com \
--to=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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