22 May
2012
22 May
'12
6:42 p.m.
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