[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130220175015.GA14541@gmail.com>
Date: Wed, 20 Feb 2013 18:50:16 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Tony Luck <tony.luck@...il.com>
Cc: Clark Williams <clark.williams@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>,
Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] sched: move RR_TIMESLICE from sysctl.h to rt.h
* Tony Luck <tony.luck@...il.com> wrote:
> On Wed, Feb 20, 2013 at 7:19 AM, Clark Williams
> <clark.williams@...il.com> wrote:
> > Signed-off-by: Clark Williams <clark.williams@...il.com>
> > ---
>
> This happens to unbreak the ia64 build which is currently grumbling about:
>
> arch/ia64/kernel/init_task.c:38: error: 'RR_TIMESLICE' undeclared here
> (not in a function)
>
> So I'd be happy if it got applied directly to Linus tree before I get too big of
> a bisection gap.
Hm, didn't it get fixed via the commit below?
Thanks,
Ingo
--------------------->
commit 77852fea6e2442a0e654a9292060489895de18c7
Author: Ingo Molnar <mingo@...nel.org>
Date: Sat Feb 16 09:46:48 2013 +0100
sched/rt: Add <linux/sched/rt.h> header to <linux/init_task.h>
IA64 relied on it through sched.h inclusion:
arch/ia64/kernel/init_task.c:38:11: error: 'MAX_PRIO' undeclared here (not in a function)
arch/ia64/kernel/init_task.c:38:11: error: 'RR_TIMESLICE' undeclared here (not in a function)
Reported-by: kbuild test robot <fengguang.wu@...el.com>
Cc: Clark Williams <williams@...hat.com>
Cc: Peter Zijlstra <peterz@...radead.org>
Cc: Steven Rostedt <rostedt@...dmis.org>
Link: http://lkml.kernel.org/n/tip-xaan1twswggedMR0airtpjui@git.kernel.org
Signed-off-by: Ingo Molnar <mingo@...nel.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists