[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140508164920.GH30445@twins.programming.kicks-ass.net>
Date: Thu, 8 May 2014 18:49:20 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>, hpa@...or.com,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
nicolas.pitre@...aro.org, tglx@...utronix.de,
daniel.lezcano@...aro.org, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:sched/core] sched/idle: Reflow cpuidle_idle_call()
On Thu, May 08, 2014 at 06:33:46PM +0200, Ingo Molnar wrote:
>
> * Peter Zijlstra <peterz@...radead.org> wrote:
>
> > On Thu, May 08, 2014 at 01:56:18PM +0200, Rafael J. Wysocki wrote:
> > > The cpuidle patches I have queued up so far are on this separate branch
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git pm-cpuidle
> > >
> > > in case you'd like to pull from there.
> >
> > Ingo, can you do that? I think the patch I just posted should be
> > enough to fix up the conflict.
>
> Yeah, sounds good to me, I'll pull it into sched/core.
>
> The patch you posted is essentially a replacement for:
>
> 52c324f8a87b cpuidle: Combine cpuidle_enabled() with cpuidle_select()
>
> when it's done on top of sched/core, right?
tip/master actually, but yes.
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists