From: kbuild test robot <fengguang.wu@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org, tipbuild@zytor.com
Subject: [tip:WIP.x86/apic 12/54] kernel/irq/chip.c:293:10: error: too many arguments to function 'irq_domain_activate_irq'
Date: Thu, 14 Sep 2017 03:54:59 +0800 [thread overview]
Message-ID: <201709140358.aewNaa2R%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git WIP.x86/apic
head: ec83e24ccab662e9365a8e75c594b8fe28b258bb
commit: bf144b7b4566caa3f5f7005ae097ff6773281edb [12/54] genirq/irqdomain: Propagate early activation
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout bf144b7b4566caa3f5f7005ae097ff6773281edb
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
kernel/irq/chip.c: In function 'irq_activate':
>> kernel/irq/chip.c:293:10: error: too many arguments to function 'irq_domain_activate_irq'
return irq_domain_activate_irq(d, false);
^~~~~~~~~~~~~~~~~~~~~~~
In file included from kernel/irq/chip.c:22:0:
kernel/irq/internals.h:442:19: note: declared here
static inline int irq_domain_activate_irq(struct irq_data *data)
^~~~~~~~~~~~~~~~~~~~~~~
vim +/irq_domain_activate_irq +293 kernel/irq/chip.c
287
288 int irq_activate(struct irq_desc *desc)
289 {
290 struct irq_data *d = irq_desc_get_irq_data(desc);
291
292 if (!irqd_affinity_is_managed(d))
> 293 return irq_domain_activate_irq(d, false);
294 return 0;
295 }
296
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 6682 bytes --]
reply other threads:[~2017-09-13 19:55 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=201709140358.aewNaa2R%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tipbuild@zytor.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®