Android mainlining interest group meeting 2012

This page has information about the Android mainlining interest group meeting, planned for early 2012.

Details
The meeting will be held:
 * during Linaro Connect
 * Time: 9:30 am to 12:00 pm
 * Date: February 10, 2012
 * Location: Bordeuax 3 room at the Sofitel, Hotel
 * City: Redwood Shores, California

See http://summit.linaro.org/lcq1-12/2012-02-10/ (I think you might need a Launchpad account to see this schedule)

See the following for remote participation instructions: http://connect.linaro.org/events/remote-participation/

Here's the direct link for the meeting: http://summit.linaro.org/lcq1-12/meeting/20039/linaro-kernel-q112-android-mainlining-f2f-2/

RSVP
This meeting requires an invitation to attend, for logistical reasons. If you are interested and enthusiastic, unless we are overbooked it is likely you will get an invitation.

If you are interested in attending, please e-mail Tim Bird at: < tim (dot) bird (at) am.sony.com > and let him know.

Expected Attendees

 * Tim Bird
 * Horishi Doyu
 * Deepak Saxena
 * Dima Zavin (probably)
 * John Stultz
 * Paul McKenney (until 11:00)
 * Arnd Bergmann
 * Hisao Munakata
 * Magnus Damm - call-in (from Japan) to report on PM issues
 * Bjorn Andersson
 * Shuah Khan
 * Zach Pfeffer
 * Jason Parker

Agenda

 * Project goals
 * Ability to run AOSP on vanilla mainline kernel (not necessarily optimized)
 * Reality check - is this a valid or useful goal?
 * Other goals (maybe desire to ease Linaro integration?)
 * Review of 3.3 staging area: drivers/staging/android
 * Review of specific patches/features
 * Tim Bird - status of logger
 * Hiroshi Doyu - status of Ion
 * Magnus Damm - status of runtime PM (/wakelocks?)
 * John Stultz - ashmem & alarm-timers
 * Anton Vorontsov (Presented by JohnS): Low-memory-killer / memory notifications & idle notifiers and interactive cpufreq gov
 * What should NOT be upstream?
 * Board support
 * patches that have no hope
 * things the community would mangle...
 * Any expected future divergences?
 * Project management
 * wiki page, mailing list, blueprint, what else?
 * how can volunteers get involved?
 * framework/guidelines for involving (and not involving) Google
 * avoiding regressions for staging code (minimizing churn for working code)
 * Plans going forward
 * Collab summit logger meeting?
 * Other upcoming events (ELC, ELC Europe, future Connect events)

broken-out patch stats
Tim started trying to generate a broken-out patch set (with quilt), from the Android common tree as of August 2011. This is how far he got before he had to work on other things. The following list has 59 patches. 'remainder 32' at the end was where he stopped. Some of these are directly extracted from a single or multiple commits in the Android source tree.

This is here mainly for a quick review.