From: Matthew Garrett <mjg59@srcf.ucam.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Matt_Domsch@dell.com" <Matt_Domsch@dell.com>
Subject: Re: [PATCH v2 3/3] efi: Add support for using efivars as a pstore backend
Date: Tue, 7 Jun 2011 22:43:10 +0100 [thread overview]
Message-ID: <20110607214310.GA2712@srcf.ucam.org> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D5301E70D902F@orsmsx505.amr.corp.intel.com>
On Tue, Jun 07, 2011 at 02:35:56PM -0700, Luck, Tony wrote:
> I don't think it all that fragile. All the back ends will have
> unique names. If the user doesn't specify a pstore= argument we
> keep the current "first past the post" method. If they do, then they
> can choose which one, or specify pstore=none (or even pstore=not-bloody-likely,
> since any not matching string will disable) to turn it off altogether.
Seems fair. I'll write a patch?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-06-07 21:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 18:15 [PATCH v2 0/3] Oops capture via EFI Matthew Garrett
2011-06-07 18:16 ` [PATCH v2 1/3] pstore: Extend API Matthew Garrett
2011-06-07 18:16 ` [PATCH v2 2/3] pstore: Add extra context for writes and erases Matthew Garrett
2011-06-07 18:16 ` [PATCH v2 3/3] efi: Add support for using efivars as a pstore backend Matthew Garrett
2011-06-07 20:16 ` Luck, Tony
2011-06-07 20:25 ` Matthew Garrett
2011-06-07 20:52 ` Luck, Tony
2011-06-07 20:55 ` Matthew Garrett
2011-06-07 21:35 ` Luck, Tony
2011-06-07 21:43 ` Matthew Garrett [this message]
2011-06-07 23:24 ` Luck, Tony
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=20110607214310.GA2712@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=Matt_Domsch@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@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®