From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [PATCH v3 00/24] C6X: New architecture Date: Wed, 28 Sep 2011 16:33:05 +0200 Message-ID: <201109281633.05583.arnd@arndb.de> References: <1317155405-26235-1-git-send-email-msalter@redhat.com> <20110928091542.9b1e35afa2075106550de7be@canb.auug.org.au> Mime-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Return-path: Received: from moutng.kundenserver.de ([212.227.17.9]:54044 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753972Ab1I1OdN convert rfc822-to-8bit (ORCPT ); Wed, 28 Sep 2011 10:33:13 -0400 In-Reply-To: <20110928091542.9b1e35afa2075106550de7be@canb.auug.org.au> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Mark Salter , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, Thomas Gleixner On Wednesday 28 September 2011, Stephen Rothwell wrote: > Show Details > On Tue, 27 Sep 2011 16:29:41 -0400 Mark Salter wrote: > > > > Here is v3 of the C6X architecture patch series. Patches are > > available in 'upstream-v3' branch at: > > > > git@linux-c6x.org:/git/projects/linux-c6x-upstreaming > > Is it time for this to be included in linux-next (i.e. are you intending > to send this to Linus during the next merge window)? If so, please send > a request (cc'd to here, linux-next and linux-kernel) asking for > inclusion. I would prefer a publically fetchable tree (the tree above is > (implicitly) fetched over ssh and is so not generally available) and > branch name that does not change over time (like "for-next" or something) > but it can just be an alias for the above. > > Arnd, do you have an opinion on this? >From my perspective it can go into -next now. All the issues I have reported in version 2 have been fixed, and the comments I made this time are relatively insignificant, so I trust that Mark can fix those either between now and the merge window or provide updates during the 3.2 bug fix phase. The only thing that absolutely needs to get fixed before 3.2.0 IMO is the ptrace ABI since we can no longer change that after a release, but it should also be a trivial change. Thomas, you also had some important comments, please complain if you see those as show-stoppers for integration into linux-next. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754325Ab1I1OdP (ORCPT ); Wed, 28 Sep 2011 10:33:15 -0400 Received: from moutng.kundenserver.de ([212.227.17.9]:54044 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753972Ab1I1OdN convert rfc822-to-8bit (ORCPT ); Wed, 28 Sep 2011 10:33:13 -0400 From: Arnd Bergmann To: Stephen Rothwell Subject: Re: [PATCH v3 00/24] C6X: New architecture Date: Wed, 28 Sep 2011 16:33:05 +0200 User-Agent: KMail/1.12.2 (Linux/2.6.35-22-generic; KDE/4.3.2; x86_64; ; ) Cc: Mark Salter , linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, Thomas Gleixner References: <1317155405-26235-1-git-send-email-msalter@redhat.com> <20110928091542.9b1e35afa2075106550de7be@canb.auug.org.au> In-Reply-To: <20110928091542.9b1e35afa2075106550de7be@canb.auug.org.au> MIME-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Message-Id: <201109281633.05583.arnd@arndb.de> X-Provags-ID: V02:K0:mMzFfsrUnh2EHGeH9eKW5IvQM2YoCVixFIQByxtQu4q ezEi2pPaQEEvAZd7AwOckd66VAUj49DdK7uDGS2F39FWCgII7u Wte/SZ0zAsKL27uG9BYbY0yHvEWgrCUgYNPxY0u8R/PutqolEF /1z5t1u5o+blloieMloZOQDiAazfBPLgbeFzAcDFbpypYCqnJy abXRBl3VPn7LPC3gXCQeoGu7fxNTjzRvtwc0uZS63/CbIsHg4B aNcKk9OYmvf4e4rZElFlp4rL+iyIIqCNC8248HNf8QNNfbCggX h2bvpVxCpZD6R3e4dFniruvd9ZOnaPugL08eakdE9ObAYybbf2 IOUZhYxmxJanbz3Fn2Yo= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 28 September 2011, Stephen Rothwell wrote: > Show Details > On Tue, 27 Sep 2011 16:29:41 -0400 Mark Salter wrote: > > > > Here is v3 of the C6X architecture patch series. Patches are > > available in 'upstream-v3' branch at: > > > > git@linux-c6x.org:/git/projects/linux-c6x-upstreaming > > Is it time for this to be included in linux-next (i.e. are you intending > to send this to Linus during the next merge window)? If so, please send > a request (cc'd to here, linux-next and linux-kernel) asking for > inclusion. I would prefer a publically fetchable tree (the tree above is > (implicitly) fetched over ssh and is so not generally available) and > branch name that does not change over time (like "for-next" or something) > but it can just be an alias for the above. > > Arnd, do you have an opinion on this? >>From my perspective it can go into -next now. All the issues I have reported in version 2 have been fixed, and the comments I made this time are relatively insignificant, so I trust that Mark can fix those either between now and the merge window or provide updates during the 3.2 bug fix phase. The only thing that absolutely needs to get fixed before 3.2.0 IMO is the ptrace ABI since we can no longer change that after a release, but it should also be a trivial change. Thomas, you also had some important comments, please complain if you see those as show-stoppers for integration into linux-next. Arnd