From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: AKASHI Takahiro <akashi.tkhro@gmail.com>, u-boot@lists.denx.de
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Tom Rini <trini@konsulko.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: [PATCH v1 1/1] efi_loader: Mark a function static
Date: Mon, 21 Oct 2024 17:05:46 +0300 [thread overview]
Message-ID: <20241021140546.2969356-1-andriy.shevchenko@linux.intel.com> (raw)
efi_bootmgr_release_uridp_resource() is not used anywhere except
the same file where it is defined. Mark it static.
This helps avoiding the compiler warning:
lib/efi_loader/efi_bootmgr.c:388:14: warning: no previous prototype for ‘efi_bootmgr_release_uridp_resource’ [-Wmissing-prototypes]
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
lib/efi_loader/efi_bootmgr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/efi_loader/efi_bootmgr.c b/lib/efi_loader/efi_bootmgr.c
index 589d3996b680..79144962cd73 100644
--- a/lib/efi_loader/efi_bootmgr.c
+++ b/lib/efi_loader/efi_bootmgr.c
@@ -385,7 +385,7 @@ err:
* @ctx: event context
* Return: status code
*/
-efi_status_t efi_bootmgr_release_uridp_resource(struct uridp_context *ctx)
+static efi_status_t efi_bootmgr_release_uridp_resource(struct uridp_context *ctx)
{
efi_status_t ret = EFI_SUCCESS;
--
2.43.0.rc1.1336.g36b5255a03ac
next reply other threads:[~2024-10-21 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 14:05 Andy Shevchenko [this message]
2024-10-21 14:40 ` [PATCH v1 1/1] efi_loader: Mark a function static Ilias Apalodimas
2024-10-22 6:02 ` Heinrich Schuchardt
2024-10-22 13:18 ` Andy Shevchenko
2024-10-24 5:03 ` Heinrich Schuchardt
2024-10-24 6:26 ` Andy Shevchenko
2024-10-24 14:18 ` Tom Rini
2024-10-24 14:37 ` Andy Shevchenko
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=20241021140546.2969356-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akashi.tkhro@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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