On 05/21/2012 03:27 AM, Dechesne, Nicolas wrote:
hi,
On Fri, May 18, 2012 at 6:00 AM, Andy Green <andy.gr...@linaro.org
<mailto:andy.gr...@linaro.org>> wrote:
So I just wanted to check first with folks to make sure there
are no
objections to merging in the -compat changes, and that the
timing of
merging in these changes isn't problematic (I can happily hold
off till
this months release is done, so we don't risk any last minute
gotchas).
The only worry I can see is that now even vanilla versions of LT
kernels are basing off llct that includes Androidizaton, even
vanilla will have possibly invasive wakelock code.
It might be good to briefly audit the changes to confirm they
don't appear if CONFIG_ANDROID is off. Google might not take much
care about that case but I think it might be important for us.
like Andy, I am a bit concerned that we merge the android stuff into
the linaro-core and that we get android candies in 'vanilla' kernel.
can't we (shouldn't we) have -android on top of -core and pull
-android only into 'android' kernel? it's true that for most things,
-android is not impacting a 'vanilla' kernel, but clearly from the
outside (community *and* customers) a kernel 'tainted' with Android is
not a 'vanilla' kernel anymore...
So this re-opens the discussion we've been having since at least last
Oct in moving to a consolidated kernel.
Since Android upstreaming is an very active goal of Linaro, I think
there's strong technical value in putting the Android patches in along
with all the other Linaro trees, as it allows us to work out any sort of
incompatibilities or issues, so we can resolve them prior to being
pushed upstream.
That said, if folks really want to have a non-android linaro-core tree,
we can ask Andrey to just merge it in the same phase as he does the
Landing team trees.
thanks
-john
_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
