From: kernel test robot <lkp@intel.com>
To: Palmer Dabbelt <palmer@rivosinc.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 13096/13213] drivers/irqchip/irq-riscv-imsic-early.c:52:9: error: too many arguments to function 'riscv_ipi_set_virq_range'
Date: Thu, 16 May 2024 04:34:15 +0800 [thread overview]
Message-ID: <202405160449.hGp9BveB-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 82d92a9a1b9ea0ea52aff27cddd05009b4edad49
commit: f725fb3518e03b48a50a22f63c440cd04b41334a [13096/13213] Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
config: riscv-randconfig-001-20240516 (https://download.01.org/0day-ci/archive/20240516/202405160449.hGp9BveB-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240516/202405160449.hGp9BveB-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202405160449.hGp9BveB-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/irqchip/irq-riscv-imsic-early.c: In function 'imsic_ipi_domain_init':
>> drivers/irqchip/irq-riscv-imsic-early.c:52:9: error: too many arguments to function 'riscv_ipi_set_virq_range'
52 | riscv_ipi_set_virq_range(virq, IMSIC_NR_IPI, true);
| ^~~~~~~~~~~~~~~~~~~~~~~~
In file included from include/linux/smp.h:119,
from include/linux/lockdep.h:14,
from include/linux/spinlock.h:63,
from include/linux/sched.h:2142,
from include/linux/ratelimit.h:6,
from include/linux/dev_printk.h:16,
from include/linux/device.h:15,
from include/linux/node.h:18,
from include/linux/cpu.h:17,
from drivers/irqchip/irq-riscv-imsic-early.c:8:
arch/riscv/include/asm/smp.h:52:6: note: declared here
52 | void riscv_ipi_set_virq_range(int virq, int nr);
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +/riscv_ipi_set_virq_range +52 drivers/irqchip/irq-riscv-imsic-early.c
21a8f8a0eb35ce Anup Patel 2024-03-07 41
21a8f8a0eb35ce Anup Patel 2024-03-07 42 static int __init imsic_ipi_domain_init(void)
21a8f8a0eb35ce Anup Patel 2024-03-07 43 {
21a8f8a0eb35ce Anup Patel 2024-03-07 44 int virq;
21a8f8a0eb35ce Anup Patel 2024-03-07 45
21a8f8a0eb35ce Anup Patel 2024-03-07 46 /* Create IMSIC IPI multiplexing */
21a8f8a0eb35ce Anup Patel 2024-03-07 47 virq = ipi_mux_create(IMSIC_NR_IPI, imsic_ipi_send);
21a8f8a0eb35ce Anup Patel 2024-03-07 48 if (virq <= 0)
21a8f8a0eb35ce Anup Patel 2024-03-07 49 return virq < 0 ? virq : -ENOMEM;
21a8f8a0eb35ce Anup Patel 2024-03-07 50
21a8f8a0eb35ce Anup Patel 2024-03-07 51 /* Set vIRQ range */
21a8f8a0eb35ce Anup Patel 2024-03-07 @52 riscv_ipi_set_virq_range(virq, IMSIC_NR_IPI, true);
21a8f8a0eb35ce Anup Patel 2024-03-07 53
21a8f8a0eb35ce Anup Patel 2024-03-07 54 /* Announce that IMSIC is providing IPIs */
21a8f8a0eb35ce Anup Patel 2024-03-07 55 pr_info("%pfwP: providing IPIs using interrupt %d\n", imsic->fwnode, IMSIC_IPI_ID);
21a8f8a0eb35ce Anup Patel 2024-03-07 56
21a8f8a0eb35ce Anup Patel 2024-03-07 57 return 0;
21a8f8a0eb35ce Anup Patel 2024-03-07 58 }
21a8f8a0eb35ce Anup Patel 2024-03-07 59 #else
21a8f8a0eb35ce Anup Patel 2024-03-07 60 static void imsic_ipi_starting_cpu(void) { }
21a8f8a0eb35ce Anup Patel 2024-03-07 61 static void imsic_ipi_dying_cpu(void) { }
21a8f8a0eb35ce Anup Patel 2024-03-07 62 static int __init imsic_ipi_domain_init(void) { return 0; }
21a8f8a0eb35ce Anup Patel 2024-03-07 63 #endif
21a8f8a0eb35ce Anup Patel 2024-03-07 64
:::::: The code at line 52 was first introduced by commit
:::::: 21a8f8a0eb35ceb21e2c9ddd87468bc3b5ac87c0 irqchip: Add RISC-V incoming MSI controller early driver
:::::: TO: Anup Patel <apatel@ventanamicro.com>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-15 20:35 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=202405160449.hGp9BveB-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=palmer@rivosinc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).