From: kernel test robot <lkp@intel.com>
To: Paul Burton <paul.burton@mips.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: arch/mips/kernel/r4k-bugs64.c:171:24: warning: no previous prototype for 'do_daddi_ov'
Date: Mon, 27 Jul 2020 17:14:47 +0800 [thread overview]
Message-ID: <202007271737.xH9OFeE8%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2599 bytes --]
Hi Paul,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 92ed301919932f777713b9172e525674157e983d
commit: 071d2f0b5419d3cf80cc8ba73ec8fe2cedc4cc0c MIPS: r4k-bugs64: Limit R4k bug checks to affected systems
date: 10 months ago
config: mips-randconfig-r024-20200727 (attached as .config)
compiler: mips64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 071d2f0b5419d3cf80cc8ba73ec8fe2cedc4cc0c
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=mips
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/mips/kernel/r4k-bugs64.c:171:24: warning: no previous prototype for 'do_daddi_ov' [-Wmissing-prototypes]
171 | asmlinkage void __init do_daddi_ov(struct pt_regs *regs)
| ^~~~~~~~~~~
vim +/do_daddi_ov +171 arch/mips/kernel/r4k-bugs64.c
^1da177e4c3f41 arch/mips/kernel/cpu-bugs64.c Linus Torvalds 2005-04-16 170
^1da177e4c3f41 arch/mips/kernel/cpu-bugs64.c Linus Torvalds 2005-04-16 @171 asmlinkage void __init do_daddi_ov(struct pt_regs *regs)
^1da177e4c3f41 arch/mips/kernel/cpu-bugs64.c Linus Torvalds 2005-04-16 172 {
c3fc5cd5c5a5f4 arch/mips/kernel/cpu-bugs64.c Ralf Baechle 2013-05-29 173 enum ctx_state prev_state;
c3fc5cd5c5a5f4 arch/mips/kernel/cpu-bugs64.c Ralf Baechle 2013-05-29 174
c3fc5cd5c5a5f4 arch/mips/kernel/cpu-bugs64.c Ralf Baechle 2013-05-29 175 prev_state = exception_enter();
^1da177e4c3f41 arch/mips/kernel/cpu-bugs64.c Linus Torvalds 2005-04-16 176 daddi_ov = 1;
^1da177e4c3f41 arch/mips/kernel/cpu-bugs64.c Linus Torvalds 2005-04-16 177 regs->cp0_epc += 4;
c3fc5cd5c5a5f4 arch/mips/kernel/cpu-bugs64.c Ralf Baechle 2013-05-29 178 exception_exit(prev_state);
^1da177e4c3f41 arch/mips/kernel/cpu-bugs64.c Linus Torvalds 2005-04-16 179 }
^1da177e4c3f41 arch/mips/kernel/cpu-bugs64.c Linus Torvalds 2005-04-16 180
:::::: The code at line 171 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 25705 bytes --]
next reply other threads:[~2020-07-27 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 9:14 kernel test robot [this message]
2020-09-25 19:17 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=202007271737.xH9OFeE8%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.burton@mips.com \
/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®