From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: arch/mips/kernel/jump_label.c:93:6: warning: no previous prototype for 'jump_label_apply_nops'
Date: Mon, 25 Sep 2023 23:06:02 +0800 [thread overview]
Message-ID: <202309252207.JQFDtapt-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 6465e260f48790807eef06b583b38ca9789b6072
commit: fdfd42892f311e2b3695852036e5be23661dc590 jump_label: mips: move module NOP patching into arch code
date: 1 year, 3 months ago
config: mips-allmodconfig (https://download.01.org/0day-ci/archive/20230925/202309252207.JQFDtapt-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230925/202309252207.JQFDtapt-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/202309252207.JQFDtapt-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/mips/kernel/jump_label.c:93:6: warning: no previous prototype for 'jump_label_apply_nops' [-Wmissing-prototypes]
93 | void jump_label_apply_nops(struct module *mod)
| ^~~~~~~~~~~~~~~~~~~~~
vim +/jump_label_apply_nops +93 arch/mips/kernel/jump_label.c
91
92 #ifdef CONFIG_MODULES
> 93 void jump_label_apply_nops(struct module *mod)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-09-25 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 15:06 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-12 17:38 arch/mips/kernel/jump_label.c:93:6: warning: no previous prototype for 'jump_label_apply_nops' kernel test robot
2022-08-02 20:09 kernel test robot
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=202309252207.JQFDtapt-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=linux-kernel@vger.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.