From: Shuah Khan <skhan@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Gabriela Bittencourt <gbittencourt@lkcamp.dev>
Cc: Danilo Pereira <dpereira@lkcamp.dev>,
Pedro Orlando <porlando@lkcamp.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: linux-next: build failure after merge of the kunit-next tree
Date: Fri, 4 Oct 2024 12:36:05 -0600 [thread overview]
Message-ID: <fe9d3f82-0b2f-4f55-ad9f-fb1b8b38ad48@linuxfoundation.org> (raw)
In-Reply-To: <20241004141146.3ce262b1@canb.auug.org.au>
On 10/3/24 22:11, Stephen Rothwell wrote:
> Hi all,
>
> After merging the kunit-next tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: modpost: "utf8nlen" [fs/unicode/tests/utf8_kunit.ko] undefined!
> ERROR: modpost: "utf8ncursor" [fs/unicode/tests/utf8_kunit.ko] undefined!
> ERROR: modpost: "utf8byte" [fs/unicode/tests/utf8_kunit.ko] undefined!
> ERROR: modpost: "utf8version_is_supported" [fs/unicode/tests/utf8_kunit.ko] undefined!
>
> Caused by commit
>
> 94d8a0976d2d ("unicode: kunit: refactor selftest to kunit tests")
>
> I have used the kunit-next tree from next-20241003 for today.
>
Sorry about that. I ran other tests - but missed allmodconfig build.
I will go drop the two patches for now.
Gabriela,
Please send new patch fixing the problems.
thanks,
-- Shuah
next prev parent reply other threads:[~2024-10-04 18:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 4:11 linux-next: build failure after merge of the kunit-next tree Stephen Rothwell
2024-10-04 13:26 ` Gabriela Bittencourt
2024-10-04 18:36 ` Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-18 2:08 Stephen Rothwell
2025-08-18 16:32 ` Shuah Khan
2025-08-19 7:44 ` David Gow
2025-08-25 6:05 ` Stephen Rothwell
2025-08-26 2:15 ` Shuah Khan
2025-08-26 9:24 ` David Gow
2025-08-27 5:49 ` Shuah Khan
2025-08-27 6:37 ` David Gow
2024-02-29 4:26 Stephen Rothwell
2024-02-29 15:07 ` Shuah Khan
2024-03-01 7:15 ` David Gow
2024-03-01 10:43 ` Stephen Rothwell
2024-03-01 16:05 ` Shuah Khan
2024-03-01 20:46 ` Stephen Rothwell
2024-03-01 22:30 ` Shuah Khan
2024-03-06 15:25 ` Shuah Khan
2024-02-28 2:48 Stephen Rothwell
2024-02-28 3:26 ` Shuah Khan
2020-01-16 5:57 Stephen Rothwell
2020-01-16 11:23 ` Alan Maguire
2020-01-16 23:27 ` Rafael J. Wysocki
2020-01-10 6:43 Stephen Rothwell
2020-01-10 11:56 ` Alan Maguire
2020-01-13 21:11 ` Brendan Higgins
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=fe9d3f82-0b2f-4f55-ad9f-fb1b8b38ad48@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=dpereira@lkcamp.dev \
--cc=gbittencourt@lkcamp.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=porlando@lkcamp.dev \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).