From: kbuild test robot <lkp@intel•com>
To: Michal Simek <monstr@monstr•eu>
Cc: Stefan Asserhall <stefan.asserhall@xilinx•com>,
kbuild-all@lists•01.org, linux-arm-kernel@lists•infradead.org
Subject: [xlnx:master 118/158] drivers/irqchip/irq-xilinx-intc.c:170:10: error: implicit declaration of function 'handle_domain_irq'; did you mean 'handle_bad_irq'?
Date: Thu, 12 Mar 2020 14:45:10 +0800 [thread overview]
Message-ID: <202003121407.5k4IPsYA%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2061 bytes --]
tree: https://github.com/Xilinx/linux-xlnx master
head: 6d1ffa89fc67781a31f8119d6bf3748ef23bdf9a
commit: c70cdd6eff0dd4c628294a8cba30a54c602e6b86 [118/158] irqchip: xilinx: Use handle_domain_irq()
config: i386-randconfig-f003-20200312 (attached as .config)
compiler: gcc-7 (Debian 7.5.0-5) 7.5.0
reproduce:
git checkout c70cdd6eff0dd4c628294a8cba30a54c602e6b86
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel•com>
All errors (new ones prefixed by >>):
drivers/irqchip/irq-xilinx-intc.c: In function 'xil_intc_handle_irq':
>> drivers/irqchip/irq-xilinx-intc.c:170:10: error: implicit declaration of function 'handle_domain_irq'; did you mean 'handle_bad_irq'? [-Werror=implicit-function-declaration]
ret = handle_domain_irq(irqc->root_domain, hwirq, regs);
^~~~~~~~~~~~~~~~~
handle_bad_irq
drivers/irqchip/irq-xilinx-intc.c: In function 'xilinx_intc_of_init':
drivers/irqchip/irq-xilinx-intc.c:280:3: error: implicit declaration of function 'set_handle_irq'; did you mean 'handle_irq'? [-Werror=implicit-function-declaration]
set_handle_irq(xil_intc_handle_irq);
^~~~~~~~~~~~~~
handle_irq
cc1: some warnings being treated as errors
vim +170 drivers/irqchip/irq-xilinx-intc.c
160
161 static void xil_intc_handle_irq(struct pt_regs *regs)
162 {
163 int ret;
164 unsigned int hwirq, cpu_id = smp_processor_id();
165 struct xintc_irq_chip *irqc = per_cpu_ptr(&primary_intc, cpu_id);
166
167 do {
168 hwirq = irqc->read_fn(irqc->base + IVR);
169 if (hwirq != -1U) {
> 170 ret = handle_domain_irq(irqc->root_domain, hwirq, regs);
171 WARN_ONCE(ret, "cpu %d: Unhandled HWIRQ %d\n",
172 cpu_id, hwirq);
173 continue;
174 }
175
176 break;
177 } while (1);
178 }
179
---
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: 35938 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2020-03-12 6:45 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=202003121407.5k4IPsYA%lkp@intel.com \
--to=lkp@intel$(echo .)com \
--cc=kbuild-all@lists$(echo .)01.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=monstr@monstr$(echo .)eu \
--cc=stefan.asserhall@xilinx$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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