mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: "H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@kernel.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] EFI urgent fixes
Date: Fri, 22 Aug 2014 08:52:21 +0100	[thread overview]
Message-ID: <20140822075221.GK29733@console-pimps.org> (raw)

Hi guys, please pull the following fixes, which trade the locking
WARN_ON()s in the efivars code for the more usual lockdep_*() functions
and an arm64 EFI change that allows the gamut of runtime services to be
invoked.

The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:

  Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)

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 6a7519e81321343165f89abb8b616df186d3e57a:

  efi/arm64: Store Runtime Services revision (2014-08-22 08:45:41 +0100)

----------------------------------------------------------------
 * WARN_ON(!spin_is_locked()) always triggers on non-SMP machines.
   Swap it for the more canonical lockdep_assert_held() which always
   does the right thing - Guenter Roeck

 * Assign the correct value to efi.runtime_version on arm64 so that all
   the runtime services can be invoked - Semen Protsenko

----------------------------------------------------------------
Guenter Roeck (1):
      firmware: Do not use WARN_ON(!spin_is_locked())

Semen Protsenko (1):
      efi/arm64: Store Runtime Services revision

 arch/arm64/kernel/efi.c     | 2 ++
 drivers/firmware/efi/vars.c | 8 ++++----
 2 files changed, 6 insertions(+), 4 deletions(-)

-- 
Matt Fleming, Intel Open Source Technology Center

             reply	other threads:[~2014-08-22  7:52 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22  7:52 Matt Fleming [this message]
2014-08-22  8:15 ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2015-07-30 21:06 Matt Fleming
2015-07-31  7:56 ` Ingo Molnar
2015-05-05 16:27 Matt Fleming
2015-05-06  6:31 ` Ingo Molnar
2015-03-02 12:51 Matt Fleming
2015-03-02 13:24 ` Ingo Molnar
2015-03-02 13:35   ` Matt Fleming
2015-02-18 11:55 Matt Fleming
2015-02-18 13:43 ` Ingo Molnar
2015-02-18 16:36   ` Ard Biesheuvel
2015-02-18 16:57     ` Ingo Molnar
2014-09-25  7:31 Matt Fleming
2014-09-25 14:41 ` Ingo Molnar
2014-09-25 14:44   ` Matt Fleming
2014-09-26 11:27   ` Paul Bolle
2014-09-26 11:35     ` Ingo Molnar
2014-09-26 12:24       ` Matt Fleming
2014-09-27  5:49         ` Ingo Molnar
2014-09-26 11:44     ` Matt Fleming
2014-09-26 11:59       ` Paul Bolle
2014-09-26 12:34         ` Matt Fleming
2014-09-26 12:55           ` Paul Bolle
2014-09-27  8:04           ` Valentin Rothberg
2014-09-27  9:59             ` Paul Bolle
2014-09-08 21:55 Matt Fleming
2014-09-09  5:07 ` Ingo Molnar
2014-09-09  7:07   ` Matt Fleming
2014-09-09 14:55     ` Ingo Molnar
2014-07-14 12:54 Matt Fleming
2014-06-27 14:51 Matt Fleming
2014-06-04 16:53 Matt Fleming
2014-04-11  7:16 Matt Fleming
2014-04-11  8:27 ` Ingo Molnar
2014-02-14 13:08 Matt Fleming
2013-11-29 12:09 Matt Fleming
2013-07-11 11:16 Matt Fleming
2013-06-07 11:50 Matt Fleming
2013-06-10 21:36 ` Matt Fleming
2013-05-17 10:18 Matt Fleming
2013-04-25  8:49 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=20140822075221.GK29733@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.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

Powered by JetHome