All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [avpatel:riscv_aclint_v2 6/13] arch/riscv/kernel/sbi-ipi.c:156:2: error: too many arguments to function 'riscv_ipi_set_virq_range'
Date: Fri, 18 Jun 2021 09:24:06 +0800	[thread overview]
Message-ID: <202106180901.3O0EH1Ax-lkp@intel.com> (raw)

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

tree:   https://github.com/avpatel/linux.git riscv_aclint_v2
head:   7dfc87079d3bd32cf6acf24c246204ca31a109e2
commit: 1f552b2190b2e0b7ae50beb1b599756a2fcf498b [6/13] RISC-V: Allow marking IPIs as suitable for remote FENCEs
config: riscv-randconfig-r002-20210617 (attached as .config)
compiler: riscv32-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://github.com/avpatel/linux/commit/1f552b2190b2e0b7ae50beb1b599756a2fcf498b
        git remote add avpatel https://github.com/avpatel/linux.git
        git fetch --no-tags avpatel riscv_aclint_v2
        git checkout 1f552b2190b2e0b7ae50beb1b599756a2fcf498b
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv 

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 >>):

   arch/riscv/kernel/sbi-ipi.c: In function 'sbi_ipi_set_virq':
>> arch/riscv/kernel/sbi-ipi.c:156:2: error: too many arguments to function 'riscv_ipi_set_virq_range'
     156 |  riscv_ipi_set_virq_range(virq, BITS_PER_LONG, false);
         |  ^~~~~~~~~~~~~~~~~~~~~~~~
   In file included from arch/riscv/include/asm/tlbflush.h:11,
                    from arch/riscv/include/asm/pgtable.h:87,
                    from include/linux/pgtable.h:6,
                    from arch/riscv/include/asm/io.h:15,
                    from include/linux/io.h:13,
                    from include/linux/irq.h:20,
                    from arch/riscv/kernel/sbi-ipi.c:12:
   arch/riscv/include/asm/smp.h:113:20: note: declared here
     113 | static inline void riscv_ipi_set_virq_range(int virq, int nr)
         |                    ^~~~~~~~~~~~~~~~~~~~~~~~


vim +/riscv_ipi_set_virq_range +156 arch/riscv/kernel/sbi-ipi.c

   138	
   139	static int __init sbi_ipi_set_virq(void)
   140	{
   141		int virq;
   142		struct irq_fwspec ipi = {
   143			.fwnode		= sbi_ipi_domain->fwnode,
   144			.param_count	= 1,
   145			.param[0]	= 0,
   146		};
   147	
   148		virq = __irq_domain_alloc_irqs(sbi_ipi_domain, -1, BITS_PER_LONG,
   149					       NUMA_NO_NODE, &ipi,
   150					       false, NULL);
   151		if (virq <= 0) {
   152			pr_err("unable to alloc IRQs from SBI IPI IRQ domain\n");
   153			return -ENOMEM;
   154		}
   155	
 > 156		riscv_ipi_set_virq_range(virq, BITS_PER_LONG, false);
   157	
   158		return 0;
   159	}
   160	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 38714 bytes --]

                 reply	other threads:[~2021-06-18  1:24 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=202106180901.3O0EH1Ax-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.