On 24/01/13 10:11, Vineet Gupta wrote: > On Thursday 24 January 2013 03:22 PM, James Hogan wrote: >> Hi Vineet, >> >> On 24/01/13 08:54, Vineet Gupta wrote: >>> (3) That branch will be ARC patches on top of Linus's 3.8 rc4. Actually for my >>> development, I'd also cherry picked a few patches from linux-next (soft and hard >>> dependencies from several different *next trees) - hard ones being >>> >>> f13a366 CONFIG_GENERIC_SIGALTSTACK build breakage with asm-generic/syscalls.h [Al] >> FYI this one has now been merged into Linus' master. >> >> Cheers >> James >> > > OK thanks - but I'd rather have the patches based on a well known checkpoint - so > maybe wait for next rc. In that case you may like to merge Al's for-linus branch in the mean time, or the commit you want directly, since it's definitely gone into the master without being rebased. > Any ideas about other questions on the thread - given that several next trees are > still involved. Stephen said it's fine to merge other trees as long as you let them know so they don't rebase, or ask them which branch is best to use that won't rebase. See the following thread: https://lkml.org/lkml/2013/1/11/187 > metag doesn't seem to be on linux-next yet ? Not yet, although I think it's almost ready. I need to solicit some acks. Cheers James -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
