From: Catalin Marinas <catalin.marinas@arm•com>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: linux-arm-kernel@lists•arm.linux.org.uk, linux-next@vger•kernel.org
Subject: Re: [PATCH 00/12] Thumb-2 kernel support
Date: Wed, 23 Jul 2008 17:05:55 +0100 [thread overview]
Message-ID: <1216829155.23395.19.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20080701014529.272706d8.akpm@linux-foundation.org>
Hi Andrew,
On Tue, 2008-07-01 at 01:45 -0700, Andrew Morton wrote:
> 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.
Were the Thumb-2 patches merged in any of the -mm tree releases? I now
updated the series to the 2.6.26-rc8-mm1 kernel if you still consider
merging them (git://linux-arm.org/linux-2.6 for-akpm).
> > > 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.
Russell (and others in the ARM community), are you OK with this set of
patches being merged into 2.6.28 mainline (i.e. at the next merging
window)? If yes, do you acknowledge the patches? In the meantime, I can
rebase them on top of linux-next to check for possible merge conflicts
(or even ask for them to be pulled into linux-next).
Thanks.
--
Catalin
next prev parent reply other threads:[~2008-07-23 16:06 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
2008-07-23 16:05 ` Catalin Marinas [this message]
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=1216829155.23395.19.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)arm.linux.org.uk \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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