From: Ard Biesheuvel <ardb@kernel.org>
To: linux-efi@vger.kernel.org
Cc: dyoung@redhat.com, Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH 0/2] efi/x86: Move runtime map sysfs code into arch/x86
Date: Mon, 7 Nov 2022 09:31:32 +0100 [thread overview]
Message-ID: <20221107083134.234918-1-ardb@kernel.org> (raw)
The EFI runtime map code is only used on x86, so let's move it out of
the generic code and into arch/x86. While at it, clarify the Kconfig
description so that it gets enabled automatically when required (i.e.,
when kexec is enabled), and can only be disabled when CONFIG_EXPERT=y
Ard Biesheuvel (2):
efi: runtime-maps: Clarify purpose and enable by default for kexec
efi: x86: Move EFI runtime map sysfs code to arch/x86
arch/x86/Kconfig | 11 ++++++++
arch/x86/include/asm/efi.h | 22 +++++++++++++++
arch/x86/platform/efi/Makefile | 1 +
{drivers/firmware => arch/x86/platform}/efi/runtime-map.c | 6 ++---
drivers/firmware/efi/Kconfig | 11 --------
drivers/firmware/efi/Makefile | 1 -
drivers/firmware/efi/efi.c | 5 +---
include/linux/efi.h | 28 --------------------
8 files changed, 38 insertions(+), 47 deletions(-)
rename {drivers/firmware => arch/x86/platform}/efi/runtime-map.c (97%)
--
2.35.1
next reply other threads:[~2022-11-07 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 8:31 Ard Biesheuvel [this message]
2022-11-07 8:31 ` [PATCH 1/2] efi: runtime-maps: Clarify purpose and enable by default for kexec Ard Biesheuvel
2022-11-07 8:31 ` [PATCH 2/2] efi: x86: Move EFI runtime map sysfs code to arch/x86 Ard Biesheuvel
2022-11-08 3:46 ` [PATCH 0/2] efi/x86: Move runtime map sysfs code into arch/x86 Dave Young
2022-11-09 8:56 ` Ard Biesheuvel
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=20221107083134.234918-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=dyoung@redhat.com \
--cc=linux-efi@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.