From: Matt Fleming <matt@console-pimps.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org
Subject: [GIT PULL] EFI urgent fixes
Date: Fri, 7 Jun 2013 12:50:46 +0100 [thread overview]
Message-ID: <20130607115046.GN30420@console-pimps.org> (raw)
Hi folks,
The following changes since commit eccaf52fee8305d5207ff110950a82c100e459bc:
x86, efi: initial the local variable of DataSize to zero (2013-05-14 08:13:05 +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 d70005bfc5f47f74fb5cb77a84983ed26bf65557:
efi: Convert runtime services function ptrs (2013-06-06 11:07:07 +0100)
----------------------------------------------------------------
* More tweaking to the EFI variable anti-bricking algorithm. Quite a
few users were reporting boot regressions in v3.9. This has now been
fixed with a more accurate "minimum storage requirement to avoid
bricking" value from Samsung (5K instead of 50%) and code to trigger
garbage collection when we near our limit - Matthew Garrett.
* A small cleanup to get rid of all the void * casting that is
prevalent in the EFI code - Borislav Petkov
----------------------------------------------------------------
Borislav Petkov (1):
efi: Convert runtime services function ptrs
Matthew Garrett (1):
Modify UEFI anti-bricking code
arch/x86/boot/compressed/eboot.c | 47 ---------
arch/x86/include/asm/efi.h | 35 +++----
arch/x86/include/uapi/asm/bootparam.h | 1 -
arch/x86/platform/efi/efi.c | 188 ++++++++++++----------------------
include/linux/efi.h | 28 ++---
5 files changed, 93 insertions(+), 206 deletions(-)
--
Matt Fleming, Intel Open Source Technology Center
next reply other threads:[~2013-06-07 11:50 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 11:50 Matt Fleming [this message]
2013-06-10 21:36 ` Matt Fleming
-- 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-08-22 7:52 Matt Fleming
2014-08-22 8:15 ` 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-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=20130607115046.GN30420@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
all inboxes | Powered by JetHome®