From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: linux-efi <linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [GIT PULL] EFI fixes for v3.8
Date: Fri, 18 Jan 2013 10:29:47 +0000 [thread overview]
Message-ID: <1358504987.8203.425.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
Hi Peter,
The following changes since commit 7d1f9aeff1ee4a20b1aeb377dd0f579fe9647619:
Linux 3.8-rc4 (2013-01-17 19:25:45 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git tags/efi-for-3.8
for you to fetch changes up to 791eb564d218dabe0f9a2212916fe54240b97afb:
efivarfs: Delete dentry from dcache in efivarfs_file_write() (2013-01-18 09:43:44 +0000)
----------------------------------------------------------------
EFI fixes for v3.8
* Fix EFI boot crash on machines with > 512GB of RAM
* Fix a few oopses in efivarfs
----------------------------------------------------------------
Lingzhu Xiang (1):
efivarfs: Drop link count of the right inode
Matt Fleming (2):
efivarfs: Never return ENOENT from firmware
efivarfs: Delete dentry from dcache in efivarfs_file_write()
Nathan Zimmer (1):
efi, x86: Pass a proper identity mapping in efi_call_phys_prelog
arch/x86/platform/efi/efi_64.c | 22 +++++++++++++++++-----
drivers/firmware/efivars.c | 5 +++--
2 files changed, 20 insertions(+), 7 deletions(-)
--
Matt Fleming, Intel Open Source Technology Center
next reply other threads:[~2013-01-18 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 10:29 Matt Fleming [this message]
[not found] ` <1358504987.8203.425.camel-ZqTwcBeJ+wsBof6jY8KHXm7IUlhRatedral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-01-18 12:57 ` [GIT PULL] EFI fixes for v3.8 David Woodhouse
2013-01-29 19:03 ` 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=1358504987.8203.425.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt-hnk1s37rvnbexh+ff434mdi2o/jbrioy@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).