Date: Wed, 3 Dec 2008 21:40:25 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Gregory Haskins <gregory.haskins.ml@gmail.com>
Cc: Gregory Haskins <ghaskins@novell.com>, rostedt@goodmis.org,
       peterz@infradead.org, linux-kernel@vger.kernel.org,
       =linux-rt-users@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] Series short description
Message-ID: <20081203204025.GA31376@elte.hu>
References: <20081111142323.28477.41235.stgit@dev.haskins.net> <4936E587.40700@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4936E587.40700@gmail.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 977
Lines: 25


* Gregory Haskins <gregory.haskins.ml@gmail.com> wrote:

> Gregory Haskins wrote:
> > Hi Ingo, Steven, Peter,
> >   This series applies roughly to mainline as an enhancement to the sched_rt
> >   logic.  Peter and I were discussing some of the unecessary overhead in
> >   pull_rt_tasks() via IRC, and this is my RFC attempt to address the problem.
> >   
> 
> Hi Ingo,
>   I was putting together a refresh of this patch and I rebased on
> tip/sched/devel.  I noticed that sched/devel is on 27-rc8, which is
> obviously a little stale.  Is this the proper tree to send patches
> against, or would you prefer a different HEAD?

tip/master would be the base to use, or tip/sched/core. The sched/devel 
branch is indeed stale.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/