linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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/irqchip-fixes 6/6] arch/mips/kernel/irq.c:118:9: error: implicit declaration of function 'irq_resolve_mapping'; did you mean 'irq_dispose_mapping'?
Date: Fri, 9 Jul 2021 06:27:21 +0800	[thread overview]
Message-ID: <202107090610.n2i7MhyC-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2230 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git irq/irqchip-fixes
head:   f333d6bc4a8b2ef6c999e46c508d50277baddcd6
commit: f333d6bc4a8b2ef6c999e46c508d50277baddcd6 [6/6] irqchip/mips: Fix RCU violation when using irqdomain lookup on interrupt entry
config: mips-jmr3927_defconfig (attached as .config)
compiler: mips-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
        # https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/commit/?id=f333d6bc4a8b2ef6c999e46c508d50277baddcd6
        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/irqchip-fixes
        git checkout f333d6bc4a8b2ef6c999e46c508d50277baddcd6
        # 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 error/warnings (new ones prefixed by >>):

   arch/mips/kernel/irq.c: In function 'do_domain_IRQ':
>> arch/mips/kernel/irq.c:118:9: error: implicit declaration of function 'irq_resolve_mapping'; did you mean 'irq_dispose_mapping'? [-Werror=implicit-function-declaration]
     118 |  desc = irq_resolve_mapping(domain, hwirq);
         |         ^~~~~~~~~~~~~~~~~~~
         |         irq_dispose_mapping
>> arch/mips/kernel/irq.c:118:7: warning: assignment to 'struct irq_desc *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
     118 |  desc = irq_resolve_mapping(domain, hwirq);
         |       ^
   cc1: some warnings being treated as errors


vim +118 arch/mips/kernel/irq.c

   110	
   111	void __irq_entry do_domain_IRQ(struct irq_domain *domain, unsigned int hwirq)
   112	{
   113		struct irq_desc *desc;
   114	
   115		irq_enter();
   116		check_stack_overflow();
   117	
 > 118		desc = irq_resolve_mapping(domain, hwirq);

---
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: 12187 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-08 22:30 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=202107090610.n2i7MhyC-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).