Hi -<div><br></div><div>Linus released 3.1 a couple of days ago, I have archived the tracking androidization patchset with a pure vanilla 3.1 release basis here</div><div><br></div><div><a href="http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git;a=shortlog;h=refs/heads/linaro-androidization-3.1">http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git;a=shortlog;h=refs/heads/linaro-androidization-3.1</a></div>
<div><br></div><div>The tracking androidization tree has already moved on into Linus&#39; new pre-3.2 basis territory</div><div><br></div><div><a href="http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git;a=shortlog;h=refs/heads/linaro-androidization-tracking">http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git;a=shortlog;h=refs/heads/linaro-androidization-tracking</a></div>
<div><br></div><div>There were big file layout refactors in the mainline networking stack that caused a lot of impact network / wireless related patches, some smaller adaptations needed in gadget related patches and a little bluetooth dust.</div>
<div><br></div><div>Interestingly during the uplevel I noticed three patches (of ~470) had evidently managed to get upstream so far for 3.2</div><div><br></div><div>0419-ipv6-updates-to-privacy-addresses-per-RFC-4941.patch</div>
<div>0431-hid-debug-Show-application-usage-for-each-collection.patch</div><div>0432-hid-multitouch-Filter-collections-by-application-usa.patch</div><div><br></div><div>I am updating the affected patches in linaro-androidization-tracking directly.  I have already been automatically tagging each push, with, eg, &quot;linaro-androidization-tracking-2011-10-25-18-24-CST&quot;, so there is a history of these rebase trees being kept.</div>
<div><br></div><div>My plan after this is to perform a more aggressive squash on the refactored patchset (I would like to considerably reduce the number of &quot;internal history&quot; type patches, keeping the contributor patch logs in the squash patch&#39;s log) and moving to using just that, instead of continuing to run the patchset we started with and the refactored one simultaneously.</div>
<div><br></div><div>I am testing this against OMAP4 Panda board, soon there will be more test coverage coming for the other LEBs supported by Linaro.  We know already that some of the non-core Androidization features were broken in common-3.0 and remained broken in the starting point for this tree.  Any patches to fix things like Broadcomm WLAN or whatever that we don&#39;t use at Linaro will be very welcome.  However, we believe the all core Android features are working fine on this tree, since they result in a working Linaro Android rootfs for Panda (complete with PVR accelerated video).</div>
<div><br></div><div>-Andy</div><div><br></div><div>PS If anyone interested in this stuff is at Linaro Connect, feel free to ping me for a chat / beer</div>