linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Kees Cook <keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
	Geliang Tang <geliangtang-9Onoh4P/yGk@public.gmane.org>
Cc: Matt Fleming
	<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>,
	Anton Vorontsov <anton-9xeibp6oKSgdnm+yROfE0A@public.gmane.org>,
	Colin Cross <ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org>,
	"linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: RE: [PATCH v2] pstore: add lzo/lz4 compression support
Date: Mon, 2 May 2016 18:43:33 +0000	[thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F3A0BAF44@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <CAGXu5jLnH+RQbBzLsDhEKN+__UZnonYD85x8966cxHtEC2G2uw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

> Tony, should I take over the pstore tree? Do you have any testing
> procedures I could use? My testing is rather manual at the moment.

Kees,

Sure - I seem to be bad about keeping track of stuff here.

I don't have any good tests ... just manually crash a machine and
make sure things show up in /sys/fs/pstore

-Tony



      parent reply	other threads:[~2016-05-02 18:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 23:11 [PATCH] pstore: add lzo/lz4 compression support Kees Cook
2016-02-18 14:04 ` [PATCH v2] " Geliang Tang
2016-02-18 17:37   ` Kees Cook
     [not found]     ` <CAGXu5jKSf5Jw5sNjniQz9aSres4kG3X3Ypj_e8V5MThLz7+nJQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-04-30  2:26       ` Geliang Tang
     [not found]         ` <20160430022637.GA8702-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2016-05-02 18:35           ` Kees Cook
     [not found]             ` <CAGXu5jLnH+RQbBzLsDhEKN+__UZnonYD85x8966cxHtEC2G2uw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-02 18:43               ` Luck, Tony [this message]

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=3908561D78D1C84285E8C5FCA982C28F3A0BAF44@ORSMSX114.amr.corp.intel.com \
    --to=tony.luck-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=anton-9xeibp6oKSgdnm+yROfE0A@public.gmane.org \
    --cc=ccross-z5hGa2qSFaRBDgjK7y7TUQ@public.gmane.org \
    --cc=geliangtang-9Onoh4P/yGk@public.gmane.org \
    --cc=keescook-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).