From: kernel test robot <lkp@intel.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Jiri Slaby <jirislaby@kernel.org>
Subject: [jirislaby:lto 7/48] kernel/static_call_inline.c:504:22: warning: no previous prototype for 'sc_func_a'
Date: Tue, 28 Jun 2022 05:08:50 +0800 [thread overview]
Message-ID: <202206280510.uGOwzwNF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git lto
head: b5ee1c28376713353cb5355716949d9c6d9b416b
commit: 7968aa68d8a410363407df9a678f4027874affcb [7/48] static_call: Make static call functions visible
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220628/202206280510.uGOwzwNF-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-3) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git/commit/?id=7968aa68d8a410363407df9a678f4027874affcb
git remote add jirislaby https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux.git
git fetch --no-tags jirislaby lto
git checkout 7968aa68d8a410363407df9a678f4027874affcb
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> kernel/static_call_inline.c:504:22: warning: no previous prototype for 'sc_func_a' [-Wmissing-prototypes]
504 | __visible_on_lto int sc_func_a(int x)
| ^~~~~~~~~
vim +/sc_func_a +504 kernel/static_call_inline.c
503
> 504 __visible_on_lto int sc_func_a(int x)
505 {
506 return x+1;
507 }
508
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-06-27 21:09 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=202206280510.uGOwzwNF-lkp@intel.com \
--to=lkp@intel.com \
--cc=andi@firstfloor.org \
--cc=jirislaby@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®