From: Catalin Marinas <catalin.marinas@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-next <linux-next@vger.kernel.org>
Subject: Re: Merge request for the Thumb-2 branch
Date: Thu, 09 Jul 2009 09:57:55 +0100 [thread overview]
Message-ID: <1247129875.11409.8.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20090709100626.1e40912d.sfr@canb.auug.org.au>
Hi Stephen,
On Thu, 2009-07-09 at 10:06 +1000, Stephen Rothwell wrote:
> On Wed, 08 Jul 2009 16:34:29 +0100 Catalin Marinas <catalin.marinas@arm.com> wrote:
> >
> > On Fri, 2009-06-26 at 17:59 +0100, Catalin Marinas wrote:
> > > Could you please merge the thumb-2 branch into linux-next:
> > >
> > > git://linux-arm.org/linux-2.6.git thumb-2
> > >
> > > It adds support for compiling the ARM kernel to the Thumb-2 instruction
> > > set (16 or 32 bit opcodes) and it makes sense to check it doesn't break
> > > other things before the next merging window (it's a bit more intrusive
> > > but limited to arch/arm/* files).
[...]
> > Russell - are you OK with getting this branch merged during the next
> > window, assuming that any new comments are implemented and testing is
> > fine? If there are other issues, please let me know.
>
> From previous comments that Russell has made, I think he is OK with arm
> platforms being in linux-next separately (we already have 2 others), so I
> will add this today.
That's not a new ARM platform, it is affecting the core
arch/arm/kernel/, arch/arm/mm/ etc. files so that they can be compiled
to an alternative instruction set (mostly 16-bit instructions). So it
should eventually be merged via Russell's tree (or get his ack and push
directly)
My intention is indeed to merge this in the upcoming window (unless
Russell has any more comments to the code).
Thanks.
--
Catalin
next prev parent reply other threads:[~2009-07-09 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 16:59 Merge request for the Thumb-2 branch Catalin Marinas
2009-07-08 15:34 ` Catalin Marinas
2009-07-09 0:06 ` Stephen Rothwell
2009-07-09 8:57 ` Catalin Marinas [this message]
2009-07-09 9:30 ` Stephen Rothwell
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=1247129875.11409.8.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sfr@canb.auug.org.au \
/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