On 01/04/2013 02:28 PM, Jon Medhurst (Tixy) wrote:
On Fri, 2013-01-04 at 15:14 +0530, Viresh Kumar wrote:
On 4 January 2013 15:09, Jon Medhurst (Tixy) tixy@linaro.org wrote:
I assume we'll be moving to Linux 3.8 for the January release cycle?
For the 13.01 my plan was to stay at 3.7 plus the stable 3.7.y updates (as by the time of code freeze the mainline would be at v3.8-rc4 or so - not sure if -rc4 would be stable enough).
But if the topic owners fill comfortable with moving to 3.8, we can go that way. Just would like to get confirmations from the owners of the heaviest topics.
For my part I have prepared a 3.8 branch for vexpress [1] which doesn't yet contain Android patches or bit.LITTLE MP as their respective branches aren't on 3.8 yet.
big.LITTLE MP is 3.8 based now :)
I take it as the vexpress topic (for the ll tree) and the big.LITTLE topic (for the llct tree) are ready to switch to 3.8, correct?
This leaves the Android topic for llct (John?) and Samsung LT topic for ll (Tushar?).
If anyone has another topic branch to include into 13.01 release, and moving to 3.8 or staying at 3.7.y is critical for that topic, please chime in!
:-) I've now included that in my integration-next branch and Android boots on this, even though we don't have any of the Android patches?! (I'm sure that never used to be possible.) Of course, we're missing important things like the interactive governor...
If we're definitely moving to 3.8 then I may soon drop my temporary 'next' branches and move 'tracking' branches to 3.8, so if anyone can't see integration-next in my tree, use integration-{linux,android}-vexpress
Yes, "definitely moving to 3.8" would make my life a bit easier too: llct could be moved to 3.8 w/o causing any troubles for topic owners (otherwise they would have to switch to linux-linaro-core-3.7 branch), and there would be no urgency in creating CI jobs for linux-linaro-core-3.7.
BTW, when booting I see the lockdep error also reported upstream: https://lkml.org/lkml/2013/1/3/192
It looks like there is some progress in getting the fix, so it could probably be resolved by 13.01 release. No 100% guarantee of course..
Thanks, Andrey