From: Liu ShuoX <shuox.liu@intel.com>
To: linux-kernel@vger.kernel.org
Cc: yanmin_zhang@linux.intel.com, keescook@chromium.org,
tony.luck@intel.com, fengguang.wu@intel.com,
Liu ShuoX <shuox.liu@intel.com>
Subject: [PATCH v3 0/3] Add a method to expand tracers for pstore easily
Date: Fri, 4 Apr 2014 11:55:56 +0800 [thread overview]
Message-ID: <1396583760-4772-1-git-send-email-shuox.liu@intel.com> (raw)
Hi,
Here are the v3 of this series.
Changelog v3:
1) Fix compiling errors when CONFIG_PSTORE_RAM=m.
Changelog v2:
1) Fix compiling errors when CONFIG_PSTORE_RAM is disabled.
2) Add some protection in the code in case we disable CONFIG_PSTORE_RAM.
---
Liu ShuoX (2):
pstore: add seq_ops for norm zone
pstore: support current records dump in ramoops
Zhang Yanmin (1):
pstore: restructure ramoops to support more trace
Documentation/ramoops.txt | 70 +++++++++++++++-
arch/x86/kernel/vmlinux.lds.S | 9 ++
drivers/platform/chrome/chromeos_pstore.c | 2 +-
fs/pstore/inode.c | 126 ++++++++++++++++++++++++++--
fs/pstore/internal.h | 4 +-
fs/pstore/platform.c | 77 +++++++++++++++--
fs/pstore/ram.c | 132 +++++++++++++++++++++++-------
fs/pstore/ram_core.c | 30 +++++++
include/linux/pstore.h | 4 +
include/linux/pstore_ram.h | 23 ++----
include/linux/pstore_ramoops.h | 78 ++++++++++++++++++
11 files changed, 490 insertions(+), 65 deletions(-)
create mode 100644 include/linux/pstore_ramoops.h
--
1.8.3.2
next reply other threads:[~2014-04-04 3:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 3:55 Liu ShuoX [this message]
2014-04-04 3:55 ` [PATCH v3 1/3] pstore: restructure ramoops to support more trace Liu ShuoX
2014-04-04 3:55 ` [PATCH v3 2/3] pstore: add seq_ops for norm zone Liu ShuoX
2014-04-04 3:55 ` [PATCH v3 3/3] pstore: support current records dump in ramoops Liu ShuoX
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=1396583760-4772-1-git-send-email-shuox.liu@intel.com \
--to=shuox.liu@intel.com \
--cc=fengguang.wu@intel.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
--cc=yanmin_zhang@linux.intel.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
all inboxes | Powered by JetHome®