From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@barebox.org>
Subject: [PATCH] efi: payload: enable both efi loader and payload for *_efi_defconfig
Date: Thu, 15 Jan 2026 13:03:33 +0100 [thread overview]
Message-ID: <20260115120333.3432231-1-a.fatoum@barebox.org> (raw)
We already have an efi_defconfig that's only for use as EFI payload/app.
Let's have all _efi_defconfig thus enable both efi-payload and efi
loader support for extra coverage.
Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
Makefile | 2 ++
arch/arm/Makefile | 6 ++----
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Makefile b/Makefile
index 9c70aa0f49a3..6da8db039b5e 100644
--- a/Makefile
+++ b/Makefile
@@ -619,6 +619,8 @@ endif
%_efiloader_defconfig: FORCE
$(call merge_into_defconfig,$*_defconfig,efi-loader)
+%_efi_defconfig: FORCE
+ $(call merge_into_defconfig,$*_defconfig,efi-loader efi-payload)
config: outputmakefile scripts_basic FORCE
$(Q)$(MAKE) $(build)=scripts/kconfig KCONFIG_DEFCONFIG_LIST= $@
diff --git a/arch/arm/Makefile b/arch/arm/Makefile
index 5efc4c3457db..b38f694339a4 100644
--- a/arch/arm/Makefile
+++ b/arch/arm/Makefile
@@ -8,13 +8,11 @@ am335x_mlo_sdmmc_defconfig:
am335x_mlo_rawflash_defconfig:
$(call merge_into_defconfig,am335x_mlo_defconfig,nomci)
-multi_v8_efi_defconfig:
- $(call merge_into_defconfig,multi_v8_defconfig,efi-payload)
-generated_configs += multi_v8_efi_defconfig
-
# Generic rule applying the fragment is in top-level Makefile
generated_configs += $(patsubst %_defconfig,%_efiloader_defconfig, \
multi_v7_defconfig multi_v8_defconfig)
+generated_configs += $(patsubst %_defconfig,%_efi_defconfig, \
+ multi_v8_defconfig)
KBUILD_CPPFLAGS += -D__ARM__ -fno-strict-aliasing
# Explicitly specifiy 32-bit ARM ISA since toolchain default can be -mthumb:
--
2.47.3
next reply other threads:[~2026-01-15 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 12:03 Ahmad Fatoum [this message]
2026-01-19 9:56 ` Sascha Hauer
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=20260115120333.3432231-1-a.fatoum@barebox.org \
--to=a.fatoum@barebox.org \
--cc=barebox@lists.infradead.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