public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the input tree
Date: Wed, 25 Mar 2026 16:22:30 +0000	[thread overview]
Message-ID: <acQLxuMKNAbtQDef@sirena.org.uk> (raw)

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

Hi all,

After merging the input tree, today's linux-next build (x86_64
allmodconfig) failed like this:

/tmp/next/build/drivers/input/touchscreen/mxs-lradc-ts.c:
In function 'mxs_lradc_ts_handle_irq':
/tmp/next/build/drivers/input/touchscreen/mxs-lradc-ts.c:508:8: error:
macro "class_spinlock_irqsave_constructor" passed 2 arguments, but takes
just 1
  508 |                 scoped_guard(spinlock_irqsave, &ts->lock, flags) {
      | ^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /tmp/next/build/include/linux/sched.h:37,
                 from /tmp/next/build/include/linux/ratelimit.h:6,
                 from /tmp/next/build/include/linux/dev_printk.h:16,
                 from /tmp/next/build/include/linux/device.h:15,
                 from /tmp/next/build/drivers/input/touchscreen/mxs-lradc-ts.c:13:
/tmp/next/build/include/linux/spinlock.h:623:9: note: macro
"class_spinlock_irqsave_constructor" defined here
  623 | #define class_spinlock_irqsave_constructor(_T) WITH_LOCK_GUARD_1_ATTRS(spinlock_irqsave, _T)
      |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /tmp/next/build/include/linux/jump_label.h:78,
                 from /tmp/next/build/include/linux/dynamic_debug.h:6,
                 from /tmp/next/build/include/linux/printk.h:620,
                 from /tmp/next/build/include/asm-generic/bug.h:31,
                 from /tmp/next/build/arch/x86/include/asm/bug.h:193,
                 from /tmp/next/build/arch/x86/include/asm/alternative.h:9,
                 from /tmp/next/build/arch/x86/include/asm/segment.h:6,
                 from /tmp/next/build/arch/x86/include/asm/ptrace.h:5,
                 from /tmp/next/build/arch/x86/include/asm/math_emu.h:5,
                 from /tmp/next/build/arch/x86/include/asm/processor.h:13,
                 from /tmp/next/build/include/linux/sched.h:13:
/tmp/next/build/include/linux/cleanup.h:300:17: error: invalid initializer
  300 |                 class_##_name##_constructor
      |                 ^~~~~~
/tmp/next/build/include/linux/cleanup.h:438:14: note: in expansion of
macro 'CLASS'
  438 |         for (CLASS(_name, scope)(args);                                 \
      |              ^~~~~
/tmp/next/build/include/linux/cleanup.h:447:9: note: in expansion of macro
'__scoped_guard'
  447 |         __scoped_guard(_name, __UNIQUE_ID(label), args)
      |         ^~~~~~~~~~~~~~
/tmp/next/build/drivers/input/touchscreen/mxs-lradc-ts.c:508:17: note:
in expansion of macro 'scoped_guard'
  508 |                 scoped_guard(spinlock_irqsave, &ts->lock, flags) {
      |                 ^~~~~~~~~~~~

Caused by commit

  a995f3ca3bd51 (Input: mxs-lradc-ts - use guard notation when acquiring spinlock)

I have used the tree from next-20260324 instead.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-03-25 16:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 16:22 Mark Brown [this message]
2026-03-25 16:25 ` linux-next: build failure after merge of the input tree Dmitry Torokhov
  -- strict thread matches above, loose matches on Subject: below --
2025-07-02  3:47 Stephen Rothwell
2025-07-02  4:01 ` Dmitry Torokhov
2022-10-24 23:00 Stephen Rothwell
2022-10-25  5:02 ` Dmitry Torokhov
2022-08-17  0:00 Stephen Rothwell
2022-08-17  0:07 ` Stephen Rothwell
2022-08-17  4:43 ` Uwe Kleine-König
2022-08-01 21:44 broonie
2022-08-04 12:33 ` Mark Brown
2022-08-04 23:36   ` Jiri Kosina
2022-04-27  0:48 Stephen Rothwell
2022-04-27  6:53 ` Fabien Parent
2022-04-27  7:35   ` Lee Jones
2022-04-27  7:41     ` Fabien Parent
2022-05-02  2:17 ` Stephen Rothwell
2022-05-06  0:25   ` Dmitry Torokhov
2022-05-31 10:13     ` Fabien Parent
2020-03-25  7:16 Stephen Rothwell
2020-03-31 21:06 ` Stephen Rothwell
2015-10-16  2:19 Stephen Rothwell
2015-10-16  7:37 ` Hans de Goede
2015-10-17 16:39   ` Dmitry Torokhov
2015-07-24  1:49 Stephen Rothwell
2015-07-24  2:33 ` Dmitry Torokhov
2012-10-05  1:47 Stephen Rothwell
2012-10-05  6:12 ` Dmitry Torokhov
2012-01-24  3:25 Stephen Rothwell
2012-01-24  6:59 ` Dmitry Torokhov
2012-01-24 23:16 ` John Stultz
2010-08-19  1:35 Stephen Rothwell
2010-08-19  5:19 ` Dmitry Torokhov

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=acQLxuMKNAbtQDef@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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