From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Catalin Marinas <catalin.marinas@arm•com>
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, 9 Jul 2009 10:06:26 +1000 [thread overview]
Message-ID: <20090709100626.1e40912d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1247067269.6595.44.camel@pc1117.cambridge.arm.com>
[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]
Hi Catalin,
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).
>
> (I'm replying to myself but I'd like to make sure this e-mail wasn't
> missed)
I am sorry, it disappeared into the morass of my inbox. :-(
> 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.
What I tell everyone: all patches/commits in the tree/series must
have been:
posted to a relevant mailing list
reviewed
unit tested
destined for the next merge window (or the current release)
*before* they are included. The linux-next tree is for integration
testing and to lower the impact of conflicts between subsystems in the
next merge window.
Basically, this should be just what you would send to Linus, or in this
case, Russell (or ask him to fetch). It is allowed to be rebased if you
deem it necessary.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-07-09 0:06 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 [this message]
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=20090709100626.1e40912d.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=catalin.marinas@arm$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux@arm$(echo .)linux.org.uk \
/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