linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, linux-next@vger.kernel.org
Subject: Re: [PATCH 00/12] Thumb-2 kernel support
Date: Tue, 1 Jul 2008 01:45:29 -0700	[thread overview]
Message-ID: <20080701014529.272706d8.akpm@linux-foundation.org> (raw)
In-Reply-To: <1214901131.29199.31.camel@pc1117.cambridge.arm.com>

On Tue, 01 Jul 2008 09:32:11 +0100 Catalin Marinas <catalin.marinas@arm.com> wrote:

> On Mon, 2008-06-30 at 12:51 -0700, Andrew Morton wrote:
> > On Fri, 06 Jun 2008 18:33:00 +0100
> > Catalin Marinas <catalin.marinas@arm.com> 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.

  reply	other threads:[~2008-07-01  8:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080606173300.7930.31525.stgit@pc1117.cambridge.arm.com>
2008-06-30 19:51 ` [PATCH 00/12] Thumb-2 kernel support Andrew Morton
2008-07-01  8:32   ` Catalin Marinas
2008-07-01  8:45     ` Andrew Morton [this message]
2008-07-23 16:05       ` Catalin Marinas
2008-07-23 20:01         ` Andrew Morton
2008-07-23 21:10           ` Catalin Marinas
2008-07-23 22:10             ` Andrew Morton
2008-07-24  8:28               ` Catalin Marinas
2008-07-27 11:08               ` Russell King - ARM Linux
2008-07-28 11:45                 ` Catalin Marinas
2008-07-28 12:40                   ` Catalin Marinas
2008-07-28 12:53                     ` Russell King - ARM Linux
2008-08-12  2:07                       ` Nicolas Pitre
2008-07-28 12:50                   ` Russell King - ARM Linux
2008-07-28 14:41                     ` Catalin Marinas
2008-08-12  2:17                     ` Nicolas Pitre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080701014529.272706d8.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-next@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).