=== Highlights === * Pushed a handful of cleanup patches from the linaro-android tree to AOSP and got them merged into the Android tree * Went on vacation from 5/9 -> 5/16 * Got back from vacation, managed to churn through most of my email. * Updated the linaro-android-3.4 tree w/ the latest bits from the AOSP tree * Started discussions about integrating android-3.4-compat tree w/ linaro-android-3.4 * Met with Deepak and started generating details for Android upstreaming session at connect * Synced with Rafael about wakelock patch status for 3.5 * Synced with Anton about his recent ramconsole work
=== Plans === * Get back to falloc volatile range rework * Address Hugh Dickins' ashmem patch * Prep some time related patches for 3.5 merge window * Further prep for remote Linaro Connect attendence
=== Issues === NA
On Fri, May 18, 2012 at 05:52:23PM -0700, John Stultz wrote:
- Synced with Rafael about wakelock patch status for 3.5
Aha! And what's the situation with this?
- Synced with Anton about his recent ramconsole work
Looks like this is going really well -- congrats.
On Mon, May 21, 2012 at 09:59:54AM -0700, John Stultz wrote:
On 05/21/2012 07:25 AM, Christian Robottom Reis wrote:
On Fri, May 18, 2012 at 05:52:23PM -0700, John Stultz wrote:
- Synced with Rafael about wakelock patch status for 3.5
Aha! And what's the situation with this?
Its still queued for 3.5.
How useful will this be once merged -- I guess I'm asking a) how much effort it is to port to and b) how probable Android is to liking it.
On 05/21/2012 10:02 AM, Christian Robottom Reis wrote:
On Mon, May 21, 2012 at 09:59:54AM -0700, John Stultz wrote:
On 05/21/2012 07:25 AM, Christian Robottom Reis wrote:
On Fri, May 18, 2012 at 05:52:23PM -0700, John Stultz wrote:
- Synced with Rafael about wakelock patch status for 3.5
Aha! And what's the situation with this?
Its still queued for 3.5.
How useful will this be once merged -- I guess I'm asking a) how much effort it is to port to and b) how probable Android is to liking it.
a) Small b) Very
Arve has been working with Rafael as the patches have been developed. The current Android 3.4 tree already shims internal wakelocks over the already upstreamed wakeup sources. http://git.linaro.org/gitweb?p=people/jstultz/android.git%3Ba=commitdiff%3Bh...
Rafael's patches really just provide: 1) The userland wakelock interface (designed to be compatible w/ Android's) and 2) A new option for configuring aggressive suspend.
Once that core work has landed, then we can migrate the Android in-kernel wakelock usage over to already upstreamed wakeup_sources to un-shim things.
-john
linaro-kernel@lists.linaro.org
-
Christian Robottom Reis -
John Stultz