From: Mark Brown <broonie@kernel.org>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Zhan Xusheng" <zhanxusheng@xiaomi.com>,
"Thomas Gleixner" <tglx@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure in the final build
Date: Wed, 30 Sep 2026 14:26:49 +0100 [thread overview]
Message-ID: <ar0OGZGN0ftc20Zi@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]
Hi all,
In the final build today's linux-next build (powerpc allnoconfig) failed
like this:
/tmp/next/build/lib/vdso/gettimeofday.c: In function '__cvdso_clock_gettime_common':
/tmp/next/build/lib/vdso/gettimeofday.c:288:31: error: implicit declaration of function 'BITS_PER_TYPE'; did you mean 'BITS_PER_LONG'? [-Wimplicit-function-declaration]
288 | BUILD_BUG_ON(clock >= BITS_PER_TYPE(msk));
| ^~~~~~~~~~~~~
/tmp/next/build/include/linux/compiler_types.h:682:23: note: in definition of macro '__compiletime_assert'
682 | if (!(condition)) \
| ^~~~~~~~~
/tmp/next/build/include/linux/compiler_types.h:702:9: note: in expansion of macro '_compiletime_assert'
702 | _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/build_bug.h:51:9: note: in expansion of macro 'BUILD_BUG_ON_MSG'
51 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition)
| ^~~~~~~~~~~~~~~~
/tmp/next/build/lib/vdso/gettimeofday.c:288:9: note: in expansion of macro 'BUILD_BUG_ON'
288 | BUILD_BUG_ON(clock >= BITS_PER_TYPE(msk));
| ^~~~~~~~~~~~
Caused by commit
ca46a07c4b682 (vdso/gettimeofday: Assert that the clockid fits into the u32 bitmask)
I reverted that commit for today.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-09-30 13:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 13:26 Mark Brown [this message]
2026-09-30 13:39 ` Thomas Weißschuh
-- strict thread matches above, loose matches on Subject: below --
2026-09-25 16:09 Mark Brown
2026-09-28 14:13 ` Mark Brown
2026-09-29 16:07 ` Bjorn Helgaas
2026-09-29 21:18 ` Mark Brown
2026-08-18 20:54 Mark Brown
2026-08-18 23:49 ` Josh Poimboeuf
2026-08-19 8:09 ` Ard Biesheuvel
2026-07-13 17:48 Mark Brown
2026-07-15 15:37 ` Mark Brown
2026-07-17 13:47 ` Manuel Ebner
2026-07-17 14:35 ` Greg Kroah-Hartman
2026-07-17 14:40 ` Johan Hovold
2026-07-17 14:54 ` Mark Brown
2026-07-17 15:06 ` Johan Hovold
2026-07-07 12:11 linux-next: build warnings after merge of the kvm-arm-fixes tree Mark Brown
2026-07-07 12:58 ` linux-next: Build failure in the final build Mark Brown
2026-07-06 14:50 linux-next: build " Mark Brown
2026-07-06 14:52 ` Johannes Berg
2026-06-10 15:51 Mark Brown
2026-01-21 17:14 Mark Brown
2026-01-21 17:18 ` Miguel Ojeda
2026-01-21 17:24 ` Mark Brown
2026-01-21 18:14 ` Miguel Ojeda
2026-01-21 19:14 ` Alice Ryhl
2026-01-21 19:24 ` Miguel Ojeda
2026-01-22 11:20 ` Mark Brown
2026-01-22 0:42 ` Deborah Brouwer
2026-01-22 11:17 ` Mark Brown
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=ar0OGZGN0ftc20Zi@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tglx@kernel.org \
--cc=thomas.weissschuh@linutronix.de \
--cc=zhanxusheng@xiaomi.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
all inboxes | Powered by JetHome®