From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761905Ab3EBSsO (ORCPT ); Thu, 2 May 2013 14:48:14 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:42886 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761232Ab3EBSsN (ORCPT ); Thu, 2 May 2013 14:48:13 -0400 Date: Thu, 2 May 2013 19:48:01 +0100 From: Russell King - ARM Linux To: Stefano Stabellini Cc: Will Deacon , "xen-devel@lists.xensource.com" , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Arnd Bergmann , Nicolas Pitre , "rob.herring@calxeda.com" , Olof Johansson Subject: Re: [PATCH v10 0/2] (arm-soc for v3.10) arm: introduce psci_smp_ops Message-ID: <20130502184801.GF14496@n2100.arm.linux.org.uk> References: <20130502171516.GA3040@mudshark.cambridge.arm.com> <20130502182812.GD14496@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, May 02, 2013 at 07:42:58PM +0100, Stefano Stabellini wrote: > On Thu, 2 May 2013, Russell King - ARM Linux wrote: > > On Thu, May 02, 2013 at 06:20:32PM +0100, Stefano Stabellini wrote: > > > On Thu, 2 May 2013, Will Deacon wrote: > > > > Hi Stefano, > > > > > > > > On Thu, May 02, 2013 at 06:12:12PM +0100, Stefano Stabellini wrote: > > > > > ping > > > > > > > > Is this a ping to have this pulled into Russell's tree? > > > > > > I thought that we agreed that the patches should go via the arm-soc > > > tree, after Russell acks them. > > > > Okay, well, is there a reason for them to go through arm-soc? They > > look more like core code to me than SoC specific - they only minimally > > touch mach-virt. > > The original reason is that some SoC specific code depends on this > series (Calxeda I believe). > > But you are probably right, if you prefer that I issue a pull request > for your tree, I have no problems with that. The only issue that there is is where we are in the development cycle (almost mid merge window), and I've yet to push anything to Linus thanks to late discovery of various messups in other chunks of code submitted via my tree - I'm starting to drop stuff from my tree in the hope that I'll get back to something that's going to be suitable for mainline. I really don't want to go pulling anything else at the moment in the hope of getting what I currently have out the door. And in any case, we shouldn't be adding any new code to our trees at this point in time.