From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Morton Subject: Re: [PATCH 00/12] Thumb-2 kernel support Date: Tue, 1 Jul 2008 01:45:29 -0700 Message-ID: <20080701014529.272706d8.akpm@linux-foundation.org> References: <20080606173300.7930.31525.stgit@pc1117.cambridge.arm.com> <20080630125110.1dc5689a.akpm@linux-foundation.org> <1214901131.29199.31.camel@pc1117.cambridge.arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from smtp1.linux-foundation.org ([140.211.169.13]:54953 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751889AbYGAIqK (ORCPT ); Tue, 1 Jul 2008 04:46:10 -0400 In-Reply-To: <1214901131.29199.31.camel@pc1117.cambridge.arm.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Catalin Marinas Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-next@vger.kernel.org On Tue, 01 Jul 2008 09:32:11 +0100 Catalin Marinas wrote: > On Mon, 2008-06-30 at 12:51 -0700, Andrew Morton wrote: > > On Fri, 06 Jun 2008 18:33:00 +0100 > > Catalin Marinas wrote: > > > > > This series of patches allows the kernel to be compiled to Thumb-2 mode > > > (on ARMv7 CPUs). The patches have been posted a few times on the list > > > and the comments were implemented (hopefully I haven't missed any). > > > > > > If/when there are no more comments, I'd like the series to be merged > > > into the -mm tree if Andrew agrees. It was tested and generated against > > > the 2.6.26-rc2-mm1 kernel. > [...] > > OK, I added this tree to -mm. Nobody is likely to test or review it > > there, but at least I might pick up on any merge or build issues. > > Thanks. > > > If you're hankering for a 2.6.27 merge of this material it might be > > more appropriate to add it to linux-next. > > I aim for the ___post 2.6.27 merge window (i.e. patches available in > 2.6.28). OK, then in that case it shouldn't go into linux-next until around 2.6.27-rc1 time. > But isn't linux-next targeted to subsystem maintainers only (i.e. get > them merged via RMK's trees)? Or an "Acked-by: RMK" would be enough. An ack is always nice. But assuming there aren't any roadblocks looming, getting it into linux-next under the assumption that the code will be ready to go by the time 2.6.28 opens would make sense.