From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: drivers/firmware/efi/libstub/vsprintf.c:251:5: warning: no previous prototype for function 'efi_vsnprintf'
Date: Wed, 09 Sep 2026 06:16:51 +0200 [thread overview]
Message-ID: <202609090621.8xNKJOFX-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Ard-Biesheuvel/x86-boot-Drop-pointless-re-implementation-of-panic/20260906-150819
head: c551ec0edb0b057c415d5530905c288523a9bde8
commit: 00893af88a10aeb0548fcd863ad11e686a94957d efi/libstub: Output UTF-16 directly from vsnprintf()
date: 2 days ago
config: loongarch-allyesconfig (https://download.01.org/0day-ci/archive/20260909/202609090621.8xNKJOFX-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260909/202609090621.8xNKJOFX-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609090621.8xNKJOFX-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/firmware/efi/libstub/vsprintf.c:251:5: warning: no previous prototype for function 'efi_vsnprintf' [-Wmissing-prototypes]
251 | int efi_vsnprintf(efi_char16_t *buf, size_t size, const char *fmt, va_list ap,
| ^
drivers/firmware/efi/libstub/vsprintf.c:251:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
251 | int efi_vsnprintf(efi_char16_t *buf, size_t size, const char *fmt, va_list ap,
| ^
| static
1 warning generated.
vim +/efi_vsnprintf +251 drivers/firmware/efi/libstub/vsprintf.c
250
> 251 int efi_vsnprintf(efi_char16_t *buf, size_t size, const char *fmt, va_list ap,
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-09 4:17 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=202609090621.8xNKJOFX-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.