From: Mark Brown <broonie@kernel.org>
To: Kir Chou <note351@hotmail.com>, David Gow <davidgow@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@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 final build
Date: Thu, 2 Jul 2026 19:26:35 +0100 [thread overview]
Message-ID: <akatWxAOMy_S1G2Y@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Hi all,
After merging the kthread tree, today's linux-next build
(powerpc pseries_le_defconfig) failed like this:
ERROR: modpost: module random32_kunit uses symbol prandom_warmup from namespace EXPORTED_FOR_KUNIT_TESTING, but does not import it.
make[3]: *** [/tmp/next/build/scripts/Makefile.modpost:147: Module.symvers] Error 1
make[2]: *** [/tmp/next/build/Makefile:2134: modpost] Error 2
make[1]: *** [/tmp/next/build/Makefile:248: __sub-make] Error 2
make: *** [Makefile:248: __sub-make] Error 2
Caused by commit
2ee1282ed36ff (lib/random32: convert selftest to KUnit)
This appears to be showing up in this specific PowerPC configuration
because ppc64_defconfig turns on
CONFIG_KUNIT=m
CONFIG_KUNIT_ALL_TESTS=m
which is an unusual choice, normally defconfigs don't turn on KUnit and
when KUnit is enabled it is built in.
I have ignored this for today.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-07-02 18:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 18:26 Mark Brown [this message]
2026-07-03 5:04 ` Kir Chou
-- strict thread matches above, loose matches on Subject: below --
2026-07-13 16:48 Mark Brown
2026-07-13 18:46 ` Tyrel Datwyler
2026-06-15 14:43 Mark Brown
2026-06-15 16:21 ` Mark Brown
2026-05-18 16:21 Mark Brown
2026-05-18 19:24 ` Nathan Chancellor
2026-05-18 20:06 ` Linus Torvalds
2026-04-01 14:07 Mark Brown
2026-03-27 22:01 Mark Brown
2026-03-27 22:03 ` Mark Brown
2026-03-27 22:05 ` Mark Brown
2026-03-28 2:18 ` Steven Rostedt
2026-03-26 16:04 Mark Brown
2026-03-26 17:05 ` Danilo Krummrich
2026-01-19 22:30 Mark Brown
2026-01-19 22:37 ` Miguel Ojeda
2026-01-19 23:32 ` Mark Brown
2026-01-19 22:49 ` Danilo Krummrich
2026-01-20 8:36 ` Alice Ryhl
2026-01-20 10:01 ` Danilo Krummrich
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=akatWxAOMy_S1G2Y@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chleroy@kernel.org \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=note351@hotmail.com \
--cc=npiggin@gmail.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