From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [paulmck-rcu:dev.2023.04.26a 38/51] arch/x86/kernel/nmi.c:441:6: warning: no previous prototype for 'set_nmi_torture'
Date: Thu, 27 Apr 2023 14:27:34 +0800 [thread overview]
Message-ID: <202304271446.dk8ruOnO-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2023.04.26a
head: 56b38a90a12f76e463a7381d8cff854926fa2b59
commit: e5bf47f3a53ddfad8e0c56b6cbf048de8d82b033 [38/51] x86/nmi: Add a set_nmi_torture() function to control NMI testing
config: i386-randconfig-a001 (https://download.01.org/0day-ci/archive/20230427/202304271446.dk8ruOnO-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?id=e5bf47f3a53ddfad8e0c56b6cbf048de8d82b033
git remote add paulmck-rcu https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
git fetch --no-tags paulmck-rcu dev.2023.04.26a
git checkout e5bf47f3a53ddfad8e0c56b6cbf048de8d82b033
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 olddefconfig
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash arch/x86/kernel/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304271446.dk8ruOnO-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/nmi.c:441:6: warning: no previous prototype for 'set_nmi_torture' [-Wmissing-prototypes]
441 | void set_nmi_torture(int nmi_delay_in, bool nmi_halt1_in, bool nmi_halt2_in, bool nmi_halt3_in)
| ^~~~~~~~~~~~~~~
vim +/set_nmi_torture +441 arch/x86/kernel/nmi.c
439
440 /* Set the test values as desired. */
> 441 void set_nmi_torture(int nmi_delay_in, bool nmi_halt1_in, bool nmi_halt2_in, bool nmi_halt3_in)
442 {
443 WRITE_ONCE(nmi_delay, nmi_delay_in);
444 WRITE_ONCE(nmi_halt1, nmi_halt1_in);
445 WRITE_ONCE(nmi_halt2, nmi_halt2_in);
446 WRITE_ONCE(nmi_halt3, nmi_halt3_in);
447 pr_info("%s: Set NMI test parameters nmi_delay=%d nmi_halt1=%d nmi_halt2=%d nmi_halt3=%d\n",
448 __func__, nmi_delay, nmi_halt1, nmi_halt2, nmi_halt3);
449 }
450 EXPORT_SYMBOL_GPL(set_nmi_torture);
451
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-04-27 6:28 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=202304271446.dk8ruOnO-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@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 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.