From: Matt Fleming <matt-HNK1S37rvNbeXh+fF434Mdi2O/JbrIOy@public.gmane.org>
To: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: "linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Tom Gundersen <teg-B22kvLQNl6c@public.gmane.org>
Subject: [GIT PULL] EFI efivars.c dissection
Date: Thu, 18 Apr 2013 17:12:15 +0100 [thread overview]
Message-ID: <51701B5F.9090203@console-pimps.org> (raw)
Hi Peter,
As discussed previously, please consider pulling this into a new topic
branch, to potentially merge for v3.10. The changes move all the code in
drivers/firmware/efivars.c into new files under drivers/firmware/efi/
and moves the efivarfs code to fs/efivarfs. This allow us to pick and
choose which EFI support to compile instead of having everything under
one monolithic file. In particular, having the efivarfs code under fs/
allows building an efivarfs.ko module, which means mount(8) can
automatically load it.
It also introduces the new efivar_entry API.
The following changes since commit 07961ac7c0ee8b546658717034fe692fd12eefa9:
Linux 3.9-rc5 (2013-03-31 15:12:43 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mfleming/efi.git chainsaw
for you to fetch changes up to a9499fa7cd3fd4824a7202d00c766b269fa3bda6:
efi: split efisubsystem from efivars (2013-04-17 13:27:06 +0100)
----------------------------------------------------------------
Matt Fleming (5):
efi: move utf16 string functions to efi.h
efivars: Keep a private global pointer to efivars
efivars: efivar_entry API
efivars: Move pstore code into the new EFI directory
efivarfs: Move to fs/efivarfs
Tom Gundersen (1):
efi: split efisubsystem from efivars
MAINTAINERS | 13 +-
drivers/firmware/Kconfig | 36 +-
drivers/firmware/Makefile | 2 +-
drivers/firmware/efi/Kconfig | 39 +
drivers/firmware/efi/Makefile | 6 +
drivers/firmware/efi/efi-pstore.c | 244 +++++
drivers/firmware/efi/efi.c | 134 +++
drivers/firmware/efi/efivars.c | 617 +++++++++++
drivers/firmware/efi/vars.c | 1049 ++++++++++++++++++
drivers/firmware/efivars.c | 2171 -------------------------------------
drivers/firmware/google/gsmi.c | 30 +-
fs/Kconfig | 1 +
fs/Makefile | 1 +
fs/efivarfs/Kconfig | 12 +
fs/efivarfs/Makefile | 7 +
fs/efivarfs/file.c | 111 ++
fs/efivarfs/inode.c | 173 +++
fs/efivarfs/internal.h | 22 +
fs/efivarfs/super.c | 267 +++++
include/linux/efi.h | 134 ++-
20 files changed, 2835 insertions(+), 2234 deletions(-)
create mode 100644 drivers/firmware/efi/Kconfig
create mode 100644 drivers/firmware/efi/Makefile
create mode 100644 drivers/firmware/efi/efi-pstore.c
create mode 100644 drivers/firmware/efi/efi.c
create mode 100644 drivers/firmware/efi/efivars.c
create mode 100644 drivers/firmware/efi/vars.c
delete mode 100644 drivers/firmware/efivars.c
create mode 100644 fs/efivarfs/Kconfig
create mode 100644 fs/efivarfs/Makefile
create mode 100644 fs/efivarfs/file.c
create mode 100644 fs/efivarfs/inode.c
create mode 100644 fs/efivarfs/internal.h
create mode 100644 fs/efivarfs/super.c
--
Matt Fleming, Intel Open Source Technology Center
reply other threads:[~2013-04-18 16:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51701B5F.9090203@console-pimps.org \
--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 \
--cc=teg-B22kvLQNl6c@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).