== Highlights == * Found and fixed a few bugs in persistent_ram and pstore, the fixes are already merged; * Consolidated persistent_ram and ramoops, added ECC suppport for ramoops. This is now called 'a generic pstore RAM backend'. So persistent_ram is moved out of staging/android/ directory, and is considered useful for the rest of (i.e. non-Android) world. The backend will handle dmesg, console and tracing messages. The consolidation patches are already in linux-next, and I guess they're heading v3.5. * Sent out a bunch of patches that add console support for pstore (this is ram_console replacement). This is probably v3.6 material. * Started looking into adding tracing support to pstore. * Got a somewhat intense comments on the vmevents subsystem. The bad news is that, according to the comments, vmevent is in not a good shape: it is not generic enough to make -mm folks happy. But the good news is that -mm folks finally looked at the code itself, and we know (to some degree) what is exactly wrong with it. So, hurrah! * Not much progress on AOSP and ulmkd integration. Just built Android images to work with on my current laptop, but so far didn't look into build system itself.
== Plans == * Continue work on tracing support for pstore. * Resume work on vmevents, have some patches ready by the end of this week.
On 05/21/2012 04:04 AM, Anton Vorontsov wrote:
== Highlights ==
- Found and fixed a few bugs in persistent_ram and pstore, the fixes are already merged;
- Consolidated persistent_ram and ramoops, added ECC suppport for ramoops. This is now called 'a generic pstore RAM backend'. So persistent_ram is moved out of staging/android/ directory, and is considered useful for the rest of (i.e. non-Android) world. The backend will handle dmesg, console and tracing messages. The consolidation patches are already in linux-next, and I guess they're heading v3.5.
- Sent out a bunch of patches that add console support for pstore (this is ram_console replacement). This is probably v3.6 material.
From the recent look of things (Kees seems fairly happy with them) it seems these still could make the 3.5 merge window. What are the likely blockers that would push it back to 3.6?
Great work again on this!
thanks -john
On 05/22/2012 09:42 AM, John Stultz wrote:
On 05/21/2012 04:04 AM, Anton Vorontsov wrote:
== Highlights ==
- Found and fixed a few bugs in persistent_ram and pstore, the fixes are already merged;
- Consolidated persistent_ram and ramoops, added ECC suppport for ramoops. This is now called 'a generic pstore RAM backend'. So persistent_ram is moved out of staging/android/ directory, and is considered useful for the rest of (i.e. non-Android) world. The backend will handle dmesg, console and tracing messages. The consolidation patches are already in linux-next, and I guess they're heading v3.5.
- Sent out a bunch of patches that add console support for pstore (this is ram_console replacement). This is probably v3.6 material.
From the recent look of things (Kees seems fairly happy with them) it seems these still could make the 3.5 merge window. What are the likely blockers that would push it back to 3.6?
I guess Greg email about already closing his tree for 3.5 just settled that question for me. :P
Ohwell, 3.6 it is then.
thanks -john
linaro-kernel@lists.linaro.org