From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751643AbaBGMdK (ORCPT ); Fri, 7 Feb 2014 07:33:10 -0500 Received: from merlin.infradead.org ([205.233.59.134]:47272 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752230AbaBGMdE (ORCPT ); Fri, 7 Feb 2014 07:33:04 -0500 Date: Fri, 7 Feb 2014 13:32:38 +0100 From: Peter Zijlstra To: Nicolas Pitre Cc: Russell King , Benjamin Herrenschmidt , Preeti U Murthy , Paul Mundt , Thomas Gleixner , Ingo Molnar , "Rafael J. Wysocki" , Daniel Lezcano , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, linux-sh@vger.kernel.org, linux-pm@vger.kernel.org, linaro-kernel@lists.linaro.org Subject: Re: [PATCH v2 6/6] cpu/idle.c: move to sched/idle.c Message-ID: <20140207123238.GA9987@twins.programming.kicks-ass.net> References: <1391017513-12995-1-git-send-email-nicolas.pitre@linaro.org> <1391017513-12995-7-git-send-email-nicolas.pitre@linaro.org> <20140130152500.GB5002@laptop.programming.kicks-ass.net> <20140130162753.GF5002@laptop.programming.kicks-ass.net> <20140206164336.GU2936@laptop.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 07, 2014 at 11:09:23AM +0000, Nicolas Pitre wrote: > On Thu, 6 Feb 2014, Peter Zijlstra wrote: > > tree, tree, what's in a word. > > Something you may plant on a patch of grass? "Merging" becomes a > strange concept in that context though. :-) I do know some farmers who splice trees thought :-) > > Its in my patch stack yes. > > Quilt I suppose?? (yet another word.) Yes, I'm one of the refugee Quilt users. Comes in handy when cold too :-) > > I should get some of that into tip I suppose, been side-tracked a bit > > this week. Sorry for the delay. > > If you prefer we pile those patches (and future ones after revew) > ourselves just let me know. Future patches are likely to be more > intimate with the scheduler so I just need to know who to upstream them > through afterwards. Normally I get Ingo to pick up the queue 1-2 times a week so latency shouldn't be too bad. But we just had the merge window and then I got side-tracked rewriting all atomic implementations. So usually submit patches against tip/master unless you know there's other pending bits that conflict, in which case you can grab my queue on top of tip/master -- but I try to make sure that's usually not needed.