Hi Catalin, On Wed, 08 Jul 2009 16:34:29 +0100 Catalin Marinas <catalin.marinas@xxxxxxx> 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@xxxxxxxxxxxxxxxx http://www.canb.auug.org.au/~sfr/
Attachment:
pgpQqqZVC5iTA.pgp
Description: PGP signature
