3 ms·
"We (Google) definitely want to get back in sync with mainline (as I've mentioned earlier in this or a related thread), and we're planning on snapping up our ke
by buster 17y ago
"We (Google) definitely want to get back in sync with mainline (as I've
mentioned earlier in this or a related thread), and we're planning on
snapping up our kernel trees to 2.6.32+ once we get past various
deadlines in the near future."
yep, LKML is they place they talk about it ;) ->
http://thread.gmane.org/gmane.linux.kernel/905490/focus=907382 http://thread.gmane.org/gmane.linux.kernel/905490/focus=9073...
As for the wakelock: I'm clearly not that deep into kernel development, but the thread looks like there is also no real point against wakelocks and the android developer seems to have points as to why he did what he did. In the end, we will see if their next attempt to kernel inclusion is sane and has good points to it.
Thanks for the interesting link, though! I guess i'll read up a bit on that. :)
- buster 17y agoLinus from http://torvalds-family.blogspot.com/2010/02/happy-camper.html http://torvalds-family.blogspot.com/2010/02/happy-camper.htm...: I don't worry about out-of-tree development for odd devices too much. I wish we could merge android, but I also accept it likely being a few years away. We had similar out-of-tree issues with the SGI extreme scalability stuff, and it took quite a while before the standard kernel merged all of that.