[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140206164336.GU2936@laptop.programming.kicks-ass.net>
Date: Thu, 6 Feb 2014 17:43:36 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Nicolas Pitre <nicolas.pitre@...aro.org>
Cc: Russell King <linux@....linux.org.uk>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Preeti U Murthy <preeti@...ux.vnet.ibm.com>,
Paul Mundt <lethal@...ux-sh.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linuxppc-dev@...ts.ozlabs.org, linux-sh@...r.kernel.org,
linux-pm@...r.kernel.org, linaro-kernel@...ts.linaro.org
Subject: Re: [PATCH v2 6/6] cpu/idle.c: move to sched/idle.c
On Thu, Feb 06, 2014 at 02:09:59PM +0000, Nicolas Pitre wrote:
> Hi Peter,
>
> Did you merge those patches in your tree?
tree, tree, what's in a word. Its in my patch stack yes. I should get
some of that into tip I suppose, been side-tracked a bit this week.
Sorry for the delay.
> If so, is it published somewhere?
http://programming.kicks-ass.net/sekrit/patches.tar.bz2
It is of varying quality at best.
> That would be a good idea if that could appear in linux-next
> so to prevent people from adding more calls to cpuidle_idle_call() from
> architecture code. I'm sending you 2 additional patches right away to
> remove those that appeared in v3.14-rc1.
Yeah, once they land in tip they'll end up in -next automagically. I'll
try and get that sorted tomorrow somewhere.
--
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