public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <anton.vorontsov@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Kees Cook <keescook@chromium.org>,
	Colin Cross <ccross@android.com>, Tony Luck <tony.luck@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	John Stultz <john.stultz@linaro.org>,
	Shuah Khan <shuahkhan@gmail.com>,
	arve@android.com, Rebecca Schultz Zavin <rebecca@android.com>,
	Jesper Juhl <jj@chaosbits.net>,
	Randy Dunlap <rdunlap@xenotime.net>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Thomas Meyer <thomas@m3y3r.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Marco Stornelli <marco.stornelli@gmail.com>,
	WANG Cong <xiyou.wangcong@gmail.com>,
	linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	linaro-kernel@lists.linaro.org, patches@linaro.org,
	kernel-team@android.com
Subject: [PATCH 0/5] Some pstore/ramoops fixes
Date: Sat, 26 May 2012 06:06:50 -0700	[thread overview]
Message-ID: <20120526130650.GA6242@lizard> (raw)

Hi Greg,

In the light of Linus' response, and I said this to Colin already, I'll
just zap a prz at boot time for pstore/console interface, which means
that nowadays there shouldn't be any objections to this bunch of fixes.

These are valid fixes for v3.5, they restore old pstore's behavior
nuances, which I changed accidentaly.

Except for the last patch, which is just a fix I happened to make when
I got bored of the warning. :-) Not a regression fix, though.

Thanks,

---
 fs/pstore/inode.c          |    2 +-
 fs/pstore/ram.c            |    3 +++
 fs/pstore/ram_core.c       |   27 +++++++++++++++++----------
 include/linux/pstore_ram.h |    2 ++
 4 files changed, 23 insertions(+), 11 deletions(-)

-- 
Anton Vorontsov
Email: cbouatmailru@gmail.com

             reply	other threads:[~2012-05-26 13:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-26 13:06 Anton Vorontsov [this message]
2012-05-26 13:07 ` [PATCH 1/5] pstore/ram: Should update old dmesg buffer before reading Anton Vorontsov
2012-05-26 13:07 ` [PATCH 2/5] pstore/ram_core: Do not reset restored zone's position and size Anton Vorontsov
2012-05-26 13:07 ` [PATCH 3/5] pstore/ram_core: Factor persistent_ram_zap() out of post_init() Anton Vorontsov
2012-05-26 13:07 ` [PATCH 4/5] pstore/ram: Should zap persistent zone on unlink Anton Vorontsov
2012-05-26 13:07 ` [PATCH 5/5] pstore/inode: Make pstore_fill_super() static Anton Vorontsov
2012-06-12  1:00 ` [PATCH 0/5] Some pstore/ramoops fixes Anton Vorontsov
2012-06-12  1:44   ` Greg Kroah-Hartman
2012-06-13 23:53 ` Greg Kroah-Hartman

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=20120526130650.GA6242@lizard \
    --to=anton.vorontsov@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=arve@android.com \
    --cc=ccross@android.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.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=rdunlap@xenotime.net \
    --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