From: Shuah Khan <skhan@linuxfoundation.org>
To: "Berg, Johannes" <johannes.berg@intel.com>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"David Gow" <davidgow@google.com>,
"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>
Cc: shuah <shuah@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
KUnit Development <kunit-dev@googlegroups.com>,
Networking <netdev@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Error during building on next-20250926 - kunit.py run --alltests run
Date: Mon, 29 Sep 2025 10:07:08 -0600 [thread overview]
Message-ID: <31594439-66f1-42e4-b122-e5888bcf2e12@linuxfoundation.org> (raw)
In-Reply-To: <0f3a1bad-4e8e-473f-8f78-92a6b96450b9@linuxfoundation.org>
On 9/29/25 10:05, Shuah Khan wrote:
> On 9/29/25 01:07, Berg, Johannes wrote:
>> +Miri
>>
>> Hi Shuah,
>>
>>>> I am seeing the following error during "kunit.py run --alltests run"
>>>> next-20250926.
>>>>
>>>> $ make all compile_commands.json scripts_gdb ARCH=um O=.kunit
>>>> --jobs=16
>>>> ERROR:root:/usr/bin/ld: drivers/net/wireless/intel/iwlwifi/tests/devinfo.o: in
>>> function `devinfo_pci_ids_config':
>>>> devinfo.c:(.text+0x2d): undefined reference to `iwl_bz_mac_cfg'
>>>> collect2: error: ld returned 1 exit status
>>>> make[3]: *** [../scripts/Makefile.vmlinux:72: vmlinux.unstripped]
>>>> Error 1
>>>> make[2]: *** [/linux/linux_next/Makefile:1242: vmlinux] Error 2
>>>> make[1]: *** [/linux/linux_next/Makefile:248: __sub-make] Error 2
>>>> make: *** [Makefile:248: __sub-make] Error 2
>>
>> Yeah, really my mistake, I didn't consider what happens in the test there when iwlwifi is built but without CONFIG_IWLMVM and CONFIG_IWLMLD.
>>
>> I think we should add those to actually run their kunit tests too, which would fix the build issue, and maybe even CONFIG_IWLDVM to increase coverage of the tests in iwlwifi itself. I can send a patch for that.
>>
>> All that said, the patch that breaks it is in linux-next via iwlwifi-next but seems to actually have missed the cutoff for 6.18, so we're good for now and I suppose Miri can even squash the build fix into that later.
>>
>
> Thank you. Sounds like a plan.
>
> I will send my kunit pr to Linus then.
Later on today - I mean.
thanks,
-- Shuah
prev parent reply other threads:[~2025-09-29 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 21:11 Error during building on next-20250926 - kunit.py run --alltests run Shuah Khan
2025-09-28 21:22 ` Shuah Khan
2025-09-29 7:07 ` Berg, Johannes
2025-09-29 16:05 ` Shuah Khan
2025-09-29 16:07 ` Shuah Khan [this message]
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=31594439-66f1-42e4-b122-e5888bcf2e12@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=davidgow@google.com \
--cc=johannes.berg@intel.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=netdev@vger.kernel.org \
--cc=shuah@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox