From: kernel test robot <lkp@intel.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: [arm-platforms:irq/generic_handle_domain_irq 17/22] kernel/irq/irqdesc.c:684:3: error: implicit declaration of function '__handle_nested_irq_desc'; did you mean '__handle_nested_irq'?
Date: Wed, 28 Jul 2021 02:54:42 +0800 [thread overview]
Message-ID: <202107280236.f7vxjlBr-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2616 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/generic_handle_domain_irq
head: d3126d1af248cba3b70342748d77c2825f37eec2
commit: c0279d786ada3daa6c234a48631bf45a5a098579 [17/22] genirq: Implement handle_nested_domain_irq()
config: microblaze-randconfig-r031-20210727 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 10.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
# https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/commit/?id=c0279d786ada3daa6c234a48631bf45a5a098579
git remote add arm-platforms https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git
git fetch --no-tags arm-platforms irq/generic_handle_domain_irq
git checkout c0279d786ada3daa6c234a48631bf45a5a098579
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross ARCH=microblaze
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel/irq/irqdesc.c:679:6: error: conflicting types for 'handle_nested_domain_irq'
679 | void handle_nested_domain_irq(struct irq_domain *domain, unsigned int hwirq)
| ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from include/linux/irq.h:586,
from kernel/irq/irqdesc.c:10:
include/linux/irqdesc.h:171:5: note: previous declaration of 'handle_nested_domain_irq' was here
171 | int handle_nested_domain_irq(struct irq_domain *domain, unsigned int hwirq);
| ^~~~~~~~~~~~~~~~~~~~~~~~
kernel/irq/irqdesc.c: In function 'handle_nested_domain_irq':
>> kernel/irq/irqdesc.c:684:3: error: implicit declaration of function '__handle_nested_irq_desc'; did you mean '__handle_nested_irq'? [-Werror=implicit-function-declaration]
684 | __handle_nested_irq_desc(desc);
| ^~~~~~~~~~~~~~~~~~~~~~~~
| __handle_nested_irq
cc1: some warnings being treated as errors
vim +684 kernel/irq/irqdesc.c
678
679 void handle_nested_domain_irq(struct irq_domain *domain, unsigned int hwirq)
680 {
681 struct irq_desc *desc = irq_resolve_mapping(domain, hwirq);
682
683 if (likely(desc))
> 684 __handle_nested_irq_desc(desc);
685 }
686 EXPORT_SYMBOL_GPL(handle_nested_domain_irq);
687
---
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: 36663 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:[~2021-07-27 18:57 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=202107280236.f7vxjlBr-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).