From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master 1/5] efi: payload: drop unreferenced efi_do_execute_image()
Date: Fri, 7 Nov 2025 15:17:18 +0100 [thread overview]
Message-ID: <20251107141725.2590394-1-a.fatoum@pengutronix.de> (raw)
This function exists in efi/payload/bootm.c as efi_execute(), where it's
actually used, so drop this unused copy.
Fixes: 7b0cedb9ddb4 ("efi: payload: split image handling from legacy
handover boot and add linux x86 image filetype")
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
efi/payload/handover.c | 13 -------------
1 file changed, 13 deletions(-)
diff --git a/efi/payload/handover.c b/efi/payload/handover.c
index 82f4cb4f5286..658f3600d6a6 100644
--- a/efi/payload/handover.c
+++ b/efi/payload/handover.c
@@ -33,19 +33,6 @@
#include "image.h"
#include "setup_header.h"
-static int efi_do_execute_image(enum filetype filetype, const char *file)
-{
- efi_handle_t handle;
- struct efi_loaded_image *loaded_image;
- int ret;
-
- ret = efi_load_image(file, &loaded_image, &handle);
- if (ret)
- return ret;
-
- return efi_execute_image(handle, loaded_image, filetype);
-}
-
typedef void(*handover_fn)(void *image, struct efi_system_table *table,
struct x86_setup_header *header);
--
2.47.3
next reply other threads:[~2025-11-07 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 14:17 Ahmad Fatoum [this message]
2025-11-07 14:17 ` [PATCH master 2/5] filetype: introduce separate filetype_x86_efi_linux_image Ahmad Fatoum
2025-11-07 14:17 ` [PATCH master 3/5] efi: payload: handover: fix filetype match Ahmad Fatoum
2025-11-07 14:17 ` [PATCH master 4/5] efi: payload: reinstate error message when booting non-EFI stubbed kernel Ahmad Fatoum
2025-11-07 14:17 ` [PATCH master 5/5] efi: payload: align kernel boot status messages Ahmad Fatoum
2025-11-10 8:20 ` [PATCH master 1/5] efi: payload: drop unreferenced efi_do_execute_image() 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=20251107141725.2590394-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--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