All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: "kernel test robot" <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: drivers/firmware/efi/libstub/vsprintf.c:511:5: warning: no previous prototype for function 'efi_snprintf'
Date: Wed, 09 Sep 2026 09:12:46 +0200	[thread overview]
Message-ID: <7b9400d4-ebf4-4757-81ce-9e52295cecf4@app.fastmail.com> (raw)
In-Reply-To: <202609090804.938npPl7-lkp@intel.com>

Please stop spamming me with reports about code that appeared
on one of my branches for a brief period, was apparently pulled
into some intel LKP branch but was never submitted by me for any
kind of review.

Thanks.


On Wed, 9 Sep 2026, at 09:00, kernel test robot wrote:
> tree:   
> https://github.com/intel-lab-lkp/linux/commits/Ard-Biesheuvel/x86-boot-Drop-pointless-re-implementation-of-panic/20260906-150819
> head:   c551ec0edb0b057c415d5530905c288523a9bde8
> commit: c551ec0edb0b057c415d5530905c288523a9bde8 efi/libstub: Add 
> efi_snprintf() to construct wide strings
> date:   3 days ago
> config: loongarch-allyesconfig 
> (https://download.01.org/0day-ci/archive/20260909/202609090804.938npPl7-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/202609090804.938npPl7-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/202609090804.938npPl7-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
>    drivers/firmware/efi/libstub/vsprintf.c:274:5: warning: no previous 
> prototype for function 'efi_vsnprintf' [-Wmissing-prototypes]
>      274 | int efi_vsnprintf(efi_char16_t *buf, size_t size, const char 
> *fmt, va_list ap,
>          |     ^
>    drivers/firmware/efi/libstub/vsprintf.c:274:1: note: declare 
> 'static' if the function is not intended to be used outside of this 
> translation unit
>      274 | int efi_vsnprintf(efi_char16_t *buf, size_t size, const char 
> *fmt, va_list ap,
>          | ^
>          | static 
>>> drivers/firmware/efi/libstub/vsprintf.c:511:5: warning: no previous prototype for function 'efi_snprintf' [-Wmissing-prototypes]
>      511 | int efi_snprintf(efi_char16_t *buf, size_t size, const char 
> *fmt, ...)
>          |     ^
>    drivers/firmware/efi/libstub/vsprintf.c:511:1: note: declare 
> 'static' if the function is not intended to be used outside of this 
> translation unit
>      511 | int efi_snprintf(efi_char16_t *buf, size_t size, const char 
> *fmt, ...)
>          | ^
>          | static 
>    2 warnings generated.
>
>
> vim +/efi_snprintf +511 drivers/firmware/efi/libstub/vsprintf.c
>
>    510	
>  > 511	int efi_snprintf(efi_char16_t *buf, size_t size, const char *fmt, ...)
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2026-09-09  7:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09  7:00 drivers/firmware/efi/libstub/vsprintf.c:511:5: warning: no previous prototype for function 'efi_snprintf' kernel test robot
2026-09-09  7:12 ` Ard Biesheuvel [this message]
2026-09-09  7:44   ` Philip Li
2026-09-09  7:47     ` 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=7b9400d4-ebf4-4757-81ce-9e52295cecf4@app.fastmail.com \
    --to=ardb@kernel.org \
    --cc=lkp@intel.com \
    --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.