From: kernel test robot <lkp@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [tglx-devel:irq/core 4/47] kernel/irq/irqdesc.c:328:2: error: too few arguments to function call, single argument 'l' was not specified
Date: Tue, 29 Apr 2025 15:22:18 +0800 [thread overview]
Message-ID: <202504291538.F6iTqoKK-lkp@intel.com> (raw)
Hi Thomas,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git irq/core
head: 9e1e6415c0b340394bdae9e10d3b0a403b3123d5
commit: 7723e58c0055c0138b4e1726df06bc832530fe4b [4/47] genirq/irqdesc: Switch to lock guards
config: s390-randconfig-001-20250429 (https://download.01.org/0day-ci/archive/20250429/202504291538.F6iTqoKK-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250429/202504291538.F6iTqoKK-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/202504291538.F6iTqoKK-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
>> kernel/irq/irqdesc.c:328:2: error: too few arguments to function call, single argument 'l' was not specified
328 | scoped_guard(raw_spinlock_irq)(&desc->lock) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/cleanup.h:343:2: note: expanded from macro 'scoped_guard'
343 | __scoped_guard(_name, __UNIQUE_ID(label), args)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/cleanup.h:334:31: note: expanded from macro '__scoped_guard'
334 | for (CLASS(_name, scope)(args); \
| ~~~~~~~~~~~~~~~~~~~ ^
include/linux/spinlock.h:545:1: note: 'class_raw_spinlock_irq_constructor' declared here
545 | DEFINE_LOCK_GUARD_1(raw_spinlock_irq, raw_spinlock_t,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
546 | raw_spin_lock_irq(_T->lock),
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
547 | raw_spin_unlock_irq(_T->lock))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/cleanup.h:409:60: note: expanded from macro 'DEFINE_LOCK_GUARD_1'
409 | __DEFINE_UNLOCK_GUARD(_name, _type, _unlock, __VA_ARGS__) \
| ^
410 | __DEFINE_LOCK_GUARD_1(_name, _type, _lock)
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/cleanup.h:391:33: note: expanded from macro '\
__DEFINE_LOCK_GUARD_1'
391 | static inline class_##_name##_t class_##_name##_constructor(_type *l) \
| ^ ~~~~~~~~
<scratch space>:22:1: note: expanded from here
22 | class_raw_spinlock_irq_constructor
| ^
>> kernel/irq/irqdesc.c:328:45: error: expected ';' after expression
328 | scoped_guard(raw_spinlock_irq)(&desc->lock) {
| ^
| ;
>> kernel/irq/irqdesc.c:328:33: warning: expression result unused [-Wunused-value]
328 | scoped_guard(raw_spinlock_irq)(&desc->lock) {
| ^~~~~~~~~~~
1 warning and 2 errors generated.
vim +/l +328 kernel/irq/irqdesc.c
320
321 static ssize_t actions_show(struct kobject *kobj, struct kobj_attribute *attr, char *buf)
322 {
323 struct irq_desc *desc = container_of(kobj, struct irq_desc, kobj);
324 struct irqaction *action;
325 ssize_t ret = 0;
326 char *p = "";
327
> 328 scoped_guard(raw_spinlock_irq)(&desc->lock) {
329 for_each_action_of_desc(desc, action) {
330 ret += sysfs_emit_at(buf, ret, "%s%s", p, action->name);
331 p = ",";
332 }
333 }
334
335 if (ret)
336 ret += sysfs_emit_at(buf, ret, "\n");
337 return ret;
338 }
339 IRQ_ATTR_RO(actions);
340
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-29 7:22 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=202504291538.F6iTqoKK-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
/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