From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh " <thomas.weissschuh@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/kunit-kselftests 21/25] lib/kunit/kunit-test.c:923: undefined reference to `kunit_uapi_run_kselftest'
Date: Sat, 31 Oct 2026 17:16:06 +0100 [thread overview]
Message-ID: <202610311735.5IJZCVYR-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/kunit-kselftests
head: 08d947e58a57885e518ef1b6ab3c81f199eac864
commit: 2b26a679c2fe1852afbbe25c9916d43c3136d0c8 [21/25] kunit: uapi: Validate the usability of /proc
config: mips-randconfig-r2309-20261031 (https://download.01.org/0day-ci/archive/20261031/202610311735.5IJZCVYR-lkp@intel.com/config)
compiler: mips64-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1-1-gc4640450
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261031/202610311735.5IJZCVYR-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/202610311735.5IJZCVYR-lkp@intel.com/
All errors (new ones prefixed by >>):
mips64-linux-ld: lib/kunit/kunit-test.o: in function `kunit_uapi_test':
>> lib/kunit/kunit-test.c:923: undefined reference to `kunit_uapi_run_kselftest'
mips64-linux-ld: lib/kunit/kunit-example-test.o: in function `example_uapi_test':
lib/kunit/kunit-example-test.c:501: undefined reference to `kunit_uapi_run_kselftest'
vim +923 lib/kunit/kunit-test.c
917
918 static void kunit_uapi_test(struct kunit *test)
919 {
920 KUNIT_UAPI_EMBED_BLOB(kunit_test_uapi, "kunit-test-uapi");
921
922 if (IS_ENABLED(CONFIG_KUNIT_UAPI))
> 923 kunit_uapi_run_kselftest(test, &kunit_test_uapi);
924 else
925 kunit_skip(test, "CONFIG_KUNIT_UAPI is not enabled");
926 }
927
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-31 16:16 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=202610311735.5IJZCVYR-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.weissschuh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.