From: Mark Brown <broonie@kernel.org>
To: Lee Jones <lee@kernel.org>, Michael Tretter <m.tretter@pengutronix.de>
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 leds-lj tree
Date: Fri, 6 Mar 2026 13:47:42 +0000 [thread overview]
Message-ID: <aara_h8QDdY9N7GR@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2181 bytes --]
Hi all,
After merging the leds-lj tree, today's linux-next build (x86_64 allmodconfig)
failed like this:
/tmp/next/build/drivers/leds/led-class-multicolor.c: In function 'multi_intensity_store':
/tmp/next/build/include/linux/compiler_types.h:706:45: error: call to '__compiletime_assert_434' declared with attribute error: min(intensity_value[i], led_cdev->max_brightness) signedness error
706 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^
/tmp/next/build/include/linux/compiler_types.h:687:25: note: in definition of macro '__compiletime_assert'
687 | prefix ## suffix(); \
| ^~~~~~
/tmp/next/build/include/linux/compiler_types.h:706:9: note: in expansion of macro '_compiletime_assert'
706 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__)
| ^~~~~~~~~~~~~~~~~~~
/tmp/next/build/include/linux/build_bug.h:40:37: note: in expansion of macro 'compiletime_assert'
40 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg)
| ^~~~~~~~~~~~~~~~~~
/tmp/next/build/include/linux/minmax.h:93:9: note: in expansion of macro 'BUILD_BUG_ON_MSG'
93 | BUILD_BUG_ON_MSG(!__types_ok(ux, uy), \
| ^~~~~~~~~~~~~~~~
/tmp/next/build/include/linux/minmax.h:98:9: note: in expansion of macro '__careful_cmp_once'
98 | __careful_cmp_once(op, x, y, __UNIQUE_ID(x_), __UNIQUE_ID(y_))
| ^~~~~~~~~~~~~~~~~~
/tmp/next/build/include/linux/minmax.h:105:25: note: in expansion of macro '__careful_cmp'
105 | #define min(x, y) __careful_cmp(min, x, y)
| ^~~~~~~~~~~~~
/tmp/next/build/drivers/leds/led-class-multicolor.c:51:38: note: in expansion of macro 'min'
51 | intensity_value[i] = min(intensity_value[i],
| ^~~
Caused by commit
787130d7bc49e (leds: multicolor: Limit intensity to max_brightness of LED)
I have used the version from next-20260305 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-03-06 13:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 13:47 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-09 1:45 linux-next: build failure after merge of the leds-lj tree Stephen Rothwell
2026-01-09 9:41 ` Lee Jones
2026-01-19 18:56 ` Mark Brown
2026-01-20 8:46 ` Lee Jones
2026-01-26 22:00 ` Mark Brown
2026-02-02 14:56 ` Mark Brown
2026-02-03 18:26 ` Mark Brown
2026-02-04 9:21 ` Lee Jones
2025-03-21 4:52 Stephen Rothwell
2025-03-21 9:24 ` Lee Jones
2025-02-21 3:42 Stephen Rothwell
2024-07-12 4:48 Stephen Rothwell
2024-07-12 7:31 ` Lee Jones
2024-07-12 7:48 ` Christian Marangi
2024-07-12 8:21 ` Lee Jones
2024-07-10 6:34 Stephen Rothwell
2024-07-10 7:16 ` Lee Jones
2024-01-29 2:10 Stephen Rothwell
2024-01-31 8:56 ` Lee Jones
[not found] <20230809131733.67238c8a@canb.auug.org.au>
2023-08-09 12:53 ` Marek Vasut
2023-03-20 0:48 Stephen Rothwell
2023-03-20 1:00 ` ChiYuan Huang
2023-03-21 23:55 ` Stephen Rothwell
2023-03-22 15:28 ` Lee Jones
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=aara_h8QDdY9N7GR@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=m.tretter@pengutronix.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