public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next <linux-next@vger.kernel.org>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>
Subject: Merge request for the Thumb-2 branch
Date: Fri, 26 Jun 2009 17:59:51 +0100	[thread overview]
Message-ID: <1246035591.30717.54.camel@pc1117.cambridge.arm.com> (raw)

Hi Stephen,

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).

The commits in this branch are:

Catalin Marinas (11):
      Thumb-2: Add some .align statements to the .S files
      Thumb-2: Add macros for the unified assembler syntax
      Thumb-2: Implementation of the unified start-up and exceptions code
      Thumb-2: Implement the unified arch/arm/mm support
      Thumb-2: Implement the unified arch/arm/lib functions
      Thumb-2: Implement the unified VFP support
      Thumb-2: Implement the unified boot code
      Thumb-2: Add support for loadable modules
      Thumb-2: Pass a Thumb-2 address to the secondary CPUs to jump to
      Thumb-2: Make the uImage entry an odd number
      Thumb-2: Add Thumb-2 support to the build files

Thanks.

-- 
Catalin

             reply	other threads:[~2009-06-26 17:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-26 16:59 Catalin Marinas [this message]
2009-07-08 15:34 ` Merge request for the Thumb-2 branch Catalin Marinas
2009-07-09  0:06   ` Stephen Rothwell
2009-07-09  8:57     ` Catalin Marinas
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=1246035591.30717.54.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