From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: devel@driverdev.osuosl.org, Tony Luck <tony.luck@intel.com>,
Arnd Bergmann <arnd@arndb.de>,
patches@linaro.org, Marco Stornelli <marco.stornelli@gmail.com>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org,
Anton Vorontsov <anton.vorontsov@linaro.org>,
arve@android.com, linaro-kernel@lists.linaro.org,
John Stultz <john.stultz@linaro.org>,
Shuah Khan <shuahkhan@gmail.com>, Jesper Juhl <jj@chaosbits.net>,
Colin Cross <ccross@android.com>,
Rebecca Schultz Zavin <rebecca@android.com>,
WANG Cong <xiyou.wangcong@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
kernel-team@android.com, Thomas Meyer <thomas@m3y3r.de>
Subject: Re: [PATCH v4 0/16] Merge ram_console into pstore, and more
Date: Tue, 22 May 2012 12:04:33 -0700 [thread overview]
Message-ID: <20120522190433.GA29404@kroah.com> (raw)
In-Reply-To: <CAGXu5jJcHDWOf4Kgnz45CT0ud-zMr2SERL2ogjeJC6n64+pQZA@mail.gmail.com>
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@linuxfoundation.org> 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?
thanks,
greg k-h
next prev parent reply other threads:[~2012-05-22 19:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 14:17 Anton Vorontsov
2012-05-22 14:17 ` [PATCH 01/16] pstore/inode: Make pstore_fill_super() static Anton Vorontsov
2012-05-22 15:24 ` Kees Cook
2012-05-22 14:17 ` [PATCH 02/16] pstore/ram: Should update old dmesg buffer before reading Anton Vorontsov
2012-05-22 15:25 ` Kees Cook
2012-05-22 14:17 ` [PATCH 03/16] pstore/ram_core: Do not reset restored zone's position and size Anton Vorontsov
2012-05-22 18:06 ` Colin Cross
2012-05-23 2:35 ` [PATCH/RFC] Make sure linux_banner is the first message in log_buf Anton Vorontsov
2012-05-23 2:50 ` Linus Torvalds
2012-05-23 2:55 ` David Miller
2012-05-23 3:59 ` Anton Vorontsov
2012-05-22 14:17 ` [PATCH 04/16] pstore/ram_core: Factor persistent_ram_zap() out of post_init() Anton Vorontsov
2012-05-22 15:26 ` Kees Cook
2012-05-22 14:17 ` [PATCH 05/16] pstore/ram: Should zap persistent zone on unlink Anton Vorontsov
2012-05-22 15:27 ` Kees Cook
2012-05-22 14:17 ` [PATCH 06/16] pstore: Add console log messages support Anton Vorontsov
2012-05-22 14:17 ` [PATCH 07/16] pstore/ram: Introduce ramoops_context.max_dump_count Anton Vorontsov
2012-05-22 15:27 ` Kees Cook
2012-05-22 14:17 ` [PATCH 08/16] pstore/ram: Factor dmesg przs initialization out of probe() Anton Vorontsov
2012-05-22 15:29 ` Kees Cook
2012-05-22 14:17 ` [PATCH 09/16] pstore/ram: Factor ramoops_get_dump_prz() out of ramoops_pstore_read() Anton Vorontsov
2012-05-22 15:32 ` Kees Cook
2012-05-22 14:17 ` [PATCH 10/16] pstore/ram: Add console messages handling Anton Vorontsov
2012-05-22 15:37 ` Kees Cook
2012-05-22 14:17 ` [PATCH 11/16] pstore/ram_core: Silence some printks Anton Vorontsov
2012-05-22 14:17 ` [PATCH 12/16] pstore/ram: Add some more documentation and examples Anton Vorontsov
2012-05-22 14:17 ` [PATCH 13/16] staging/android: Remove ram_console driver Anton Vorontsov
2012-05-22 14:17 ` [PATCH 14/16] pstore/ram_core: Remove now unused code Anton Vorontsov
2012-05-22 14:17 ` [PATCH 15/16] pstore/platform: Make automatic updates interval configurable Anton Vorontsov
2012-05-22 15:39 ` Kees Cook
2012-05-22 14:17 ` [PATCH 16/16] pstore/platform: Disable automatic updates by default Anton Vorontsov
2012-05-22 15:42 ` Kees Cook
2012-05-22 18:19 ` [PATCH v4 0/16] Merge ram_console into pstore, and more Greg Kroah-Hartman
2012-05-22 18:33 ` Kees Cook
2012-05-22 19:04 ` Greg Kroah-Hartman [this message]
2012-05-22 19:09 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120522190433.GA29404@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=anton.vorontsov@linaro.org \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=ccross@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=jj@chaosbits.net \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.stornelli@gmail.com \
--cc=patches@linaro.org \
--cc=rebecca@android.com \
--cc=sboyd@codeaurora.org \
--cc=shuahkhan@gmail.com \
--cc=thomas@m3y3r.de \
--cc=tony.luck@intel.com \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome