From: kernel test robot <lkp@intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Ard Biesheuvel <ardb@kernel.org>
Subject: [linux-next:master 122/11953] arch/arm/mach-iop32x/irq.c:62:6: warning: no previous prototype for 'iop_handle_irq'
Date: Sat, 12 Mar 2022 05:35:13 +0800 [thread overview]
Message-ID: <202203120529.J5NCI7FE-lkp@intel.com> (raw)
Hi Arnd,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 71941773e143369a73c9c4a3b62fbb60736a1182
commit: 6f5d248d05db9c4991366154f1a657a630faa583 [122/11953] ARM: iop32x: use GENERIC_IRQ_MULTI_HANDLER
config: arm-randconfig-r006-20220106 (https://download.01.org/0day-ci/archive/20220312/202203120529.J5NCI7FE-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.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
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=6f5d248d05db9c4991366154f1a657a630faa583
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 6f5d248d05db9c4991366154f1a657a630faa583
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm SHELL=/bin/bash
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/arm/mach-iop32x/irq.c:62:6: warning: no previous prototype for 'iop_handle_irq' [-Wmissing-prototypes]
62 | void iop_handle_irq(struct pt_regs *regs)
| ^~~~~~~~~~~~~~
--
>> arch/arm/mach-iop32x/cp6.c:10:6: warning: no previous prototype for 'iop_enable_cp6' [-Wmissing-prototypes]
10 | void iop_enable_cp6(void)
| ^~~~~~~~~~~~~~
arch/arm/mach-iop32x/cp6.c:43:13: warning: no previous prototype for 'iop_init_cp6_handler' [-Wmissing-prototypes]
43 | void __init iop_init_cp6_handler(void)
| ^~~~~~~~~~~~~~~~~~~~
vim +/iop_handle_irq +62 arch/arm/mach-iop32x/irq.c
61
> 62 void iop_handle_irq(struct pt_regs *regs)
63 {
64 u32 mask;
65
66 iop_enable_cp6();
67
68 do {
69 mask = iintsrc_read();
70 if (mask)
71 generic_handle_irq(fls(mask));
72 } while (mask);
73 }
74
---
0-DAY CI Kernel Test Service
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-03-11 21:36 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=202203120529.J5NCI7FE-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.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.