Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760172Ab2EVTJu (ORCPT ); Tue, 22 May 2012 15:09:50 -0400 Received: from mail-bk0-f46.google.com ([209.85.214.46]:43704 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751875Ab2EVTJs convert rfc822-to-8bit (ORCPT ); Tue, 22 May 2012 15:09:48 -0400 MIME-Version: 1.0 In-Reply-To: <20120522190433.GA29404@kroah.com> References: <20120522141717.GA31574@lizard> <20120522181910.GA28826@kroah.com> <20120522190433.GA29404@kroah.com> Date: Tue, 22 May 2012 12:09:47 -0700 X-Google-Sender-Auth: k4fbefgzIsUK6WJmHZ96zN2o8Zs Message-ID: Subject: Re: [PATCH v4 0/16] Merge ram_console into pstore, and more From: Kees Cook To: Greg Kroah-Hartman Cc: devel@driverdev.osuosl.org, Tony Luck , Arnd Bergmann , patches@linaro.org, Marco Stornelli , Stephen Boyd , linux-kernel@vger.kernel.org, Anton Vorontsov , arve@android.com, linaro-kernel@lists.linaro.org, John Stultz , Shuah Khan , Jesper Juhl , Colin Cross , Rebecca Schultz Zavin , WANG Cong , Andrew Morton , kernel-team@android.com, Thomas Meyer Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-System-Of-Record: true Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1807 Lines: 47 On Tue, May 22, 2012 at 12:04 PM, Greg Kroah-Hartman 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 >> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/