From: Shuah Khan <skhan@linuxfoundation.org>
To: David Gow <davidgow@google.com>, Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Brendan Higgins <brendanhiggins@google.com>,
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-fixes tree
Date: Tue, 6 Aug 2024 16:29:34 -0600 [thread overview]
Message-ID: <ae5edb38-5f77-4104-b541-d2cf2c3011ff@linuxfoundation.org> (raw)
In-Reply-To: <9bd07238-5540-4b6b-9532-8e3590cf2b77@linuxfoundation.org>
On 8/6/24 13:20, Shuah Khan wrote:
> On 8/5/24 20:06, David Gow wrote:
>> On Tue, 6 Aug 2024 at 07:18, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>
>>> Hi all,
>>>
>>> After merging the kunit-fixes tree, today's linux-next build (powerpc
>>> ppc64_defconfig) failed like this:
>>>
>>> ERROR: modpost: "__start_rodata" [lib/kunit/kunit.ko] undefined!
>>> ERROR: modpost: "__end_rodata" [lib/kunit/kunit.ko] undefined!
>>>
>>> Caused by commit
>>>
>>> 7d3c33b290b1 ("kunit: Device wrappers should also manage driver name")
>>>
>>
>
> David,
>
> Looks like the above patch below is still under review - I can drop
> 7d3c33b290b1 for now to avoid build failures. Thoughts?
>
7d3c33b290b1 ("kunit: Device wrappers should also manage driver name")
I did drop this patch for now from linux-kselftest kunit-fixes branch.
I will pull the two patches together when the patch below is ready.
https://lore.kernel.org/linux-kselftest/20240806020136.3481593-1-davidgow@google.com/
thanks,
-- Shuah
next prev parent reply other threads:[~2024-08-06 22:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-05 23:18 linux-next: build failure after merge of the kunit-fixes tree Stephen Rothwell
2024-08-06 2:06 ` David Gow
2024-08-06 19:20 ` Shuah Khan
2024-08-06 22:29 ` Shuah Khan [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-25 10:05 Stephen Rothwell
2021-06-25 11:31 ` David Gow
2021-06-25 15:48 ` Shuah Khan
2021-06-25 9:52 Stephen Rothwell
2021-06-25 17:53 ` Daniel Latypov
2021-06-25 18:12 ` Shuah Khan
2021-06-25 18:46 ` 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=ae5edb38-5f77-4104-b541-d2cf2c3011ff@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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