All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [git pull] pstore changes
Date: Mon, 01 Aug 2011 09:56:52 -0700	[thread overview]
Message-ID: <4e36dad425294f12e2@agluck-desktop.sc.intel.com> (raw)

Hi Linus,

please pull from:

	git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git pstore-efi

This will update the files shown below - adding a new pstore backend that
uses EFI variables as persistant storage.

Thanks!

-Tony

 Documentation/ABI/testing/pstore    |    6 +
 Documentation/kernel-parameters.txt |    2 +
 drivers/acpi/apei/erst.c            |   20 ++-
 drivers/firmware/efivars.c          |  243 +++++++++++++++++++++++++++++++++--
 fs/pstore/inode.c                   |   12 +-
 fs/pstore/internal.h                |    2 +-
 fs/pstore/platform.c                |   30 +++-
 include/linux/efi.h                 |    6 +
 include/linux/pstore.h              |    9 +-
 9 files changed, 296 insertions(+), 34 deletions(-)

Matthew Garrett (5):
      pstore: Extend API for more flexibility in new backends
      pstore: Add extra context for writes and erases
      pstore: Make "part" unsigned
      pstore: Allow the user to explicitly choose a backend
      efi: Add support for using efivars as a pstore backend

Mike Waychison (4):
      efivars: String functions
      efivars: introduce utf16_strncmp
      efivars: Use string functions in pstore_write
      efivars: Introduce PSTORE_EFI_ATTRIBUTES


             reply	other threads:[~2011-08-01 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 16:56 Luck, Tony [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-10-25 17:16 [git pull] pstore changes Luck, Tony
2012-01-05 17:29 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=4e36dad425294f12e2@agluck-desktop.sc.intel.com \
    --to=tony.luck@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.