On Tue, May 22, 2012 at 12:04 PM, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Tue, May 22, 2012 at 11:33:33AM -0700, Kees Cook wrote: >> On Tue, May 22, 2012 at 11:19 AM, Greg Kroah-Hartman >> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: >> > On Tue, May 22, 2012 at 07:17:17AM -0700, Anton Vorontsov wrote: >> >> Hi all, >> >> >> >> A brand new v4: >> >> >> >> - Per Kees Cook's comments, the patches no longer remove an automatic >> >> updates feature, but instead make the it configurable; plus disable >> >> it by default (in a separate patch); >> >> - Fixed some bugs noticed by Colin Cross; >> >> - Documented new continuous ramoops-console log behaviour (also >> >> noticed by Colin Cross). >> > >> > In case you were wondering, all of this is going to have to wait for >> > 3.6, as the 3.5 merge window with my trees have been closed. I'll be >> > able to start accepting patches once 3.5-rc1 is out, so take your time >> > in getting this all working properly, there's no rush here. >> >> Will the ramoops stuff that was in -next (via -mm) that now landed in >> -staging make it sanely into 3.5? Specifically the two patches at the >> top of: >> http://git.kernel.org/?p=linux/kernel/git/kees/linux.git;a=shortlog;h=refs/heads/ramoops > > Anything that was in staging and linux-next already, yes, will go in for > 3.5, I've already sent Linus the pull request for that. > > Is that a problem? No problem at all -- it missed 3.4 on a technicality, and I didn't want it to miss 3.5 too. :) Thanks! -Kees -- Kees Cook Chrome OS Security _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
