linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] EFI urgent fix
Date: Wed, 15 Jul 2015 15:31:11 +0100	[thread overview]
Message-ID: <20150715143111.GB6955@codeblueprint.co.uk> (raw)

Folks,

Please pull the following fix from Tony that addresses a bug in the EFI
CPER driver preventing it from working with memory error records as
described in the UEFI 2.2 spec.

The following changes since commit d67e199611b986b345ea3087ee2e4a15da1c98b3:

  efi: Fix error handling in add_sysfs_runtime_map_entry() (2015-05-05 16:20:13 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-urgent

for you to fetch changes up to 4c62360d7562a20c996836d163259c87d9378120:

  efi: Handle memory error structures produced based on old versions of standard (2015-07-15 13:30:38 +0100)

----------------------------------------------------------------
 * Fix a bug in the Common Platform Error Record (CPER) driver that
   caused old UEFI spec (< 2.3) versions of the memory error record
   structure to be declared invalid - Tony Luck

----------------------------------------------------------------
Tony Luck (1):
      efi: Handle memory error structures produced based on old versions of standard

 drivers/firmware/efi/cper.c | 15 ++++++++++++---
 include/linux/cper.h        | 22 +++++++++++++++++++++-
 2 files changed, 33 insertions(+), 4 deletions(-)

-- 
Matt Fleming, Intel Open Source Technology Center

             reply	other threads:[~2015-07-15 14:31 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 14:31 Matt Fleming [this message]
2015-07-21  7:53 ` [GIT PULL] EFI urgent fix Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2017-04-12 15:27 Matt Fleming
2017-01-27 22:06 Matt Fleming
2016-05-13 20:34 Matt Fleming
2016-04-25 11:26 Matt Fleming
2016-04-25 15:29 ` Ingo Molnar
2016-04-01 19:03 Matt Fleming
2016-04-02  7:32 ` Ingo Molnar
2015-11-04 10:47 Matt Fleming
2015-11-04 10:50 ` Thomas Gleixner
2015-10-16 10:01 Matt Fleming
2015-10-16 10:04 ` Ingo Molnar
2015-10-12 14:13 Matt Fleming
2015-06-11 12:47 Matt Fleming
2015-06-11 14:43 ` Ingo Molnar
2015-06-12 15:00   ` Matt Fleming
2015-03-27 19:18 Matt Fleming
2014-09-19 10:33 Matt Fleming
2014-09-19 10:50 ` Ingo Molnar
2014-08-06  9:46 Matt Fleming
2014-07-07  6:43 Matt Fleming
2014-06-20  9:00 Matt Fleming
2014-06-20  9:28 ` Catalin Marinas
2014-06-20 13:39   ` Leif Lindholm
2014-06-20 13:49     ` Matt Fleming
2014-06-20 14:19       ` Leif Lindholm
2014-06-25 20:42 ` Matt Fleming
2014-05-03  5:51 Matt Fleming
2014-05-04 18:21 ` Ingo Molnar
2014-03-04 23:47 Matt Fleming
2013-09-19 12:41 Matt Fleming
2013-09-20  7:53 ` Ingo Molnar
2013-06-21  9:56 Matt Fleming
2013-04-26 16:30 Matt Fleming
2013-04-26 16:40 ` Linus Torvalds
2013-04-26 16:48   ` Matt Fleming

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=20150715143111.GB6955@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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).