linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Shuah Khan <skhan@linuxfoundation.org>,
	Brendan Higgins <brendanhiggins@google.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Alan Maguire <alan.maguire@oracle.com>
Subject: linux-next: build failure after merge of the kunit-next tree
Date: Thu, 16 Jan 2020 16:57:03 +1100	[thread overview]
Message-ID: <20200116165703.4e04be51@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 911 bytes --]

Hi all,

After merging the kunit-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:

x86_64-linux-gnu-ld: drivers/base/test/property-entry-test.o: in function `kunit_test_suites_init':
property-entry-test.c:(.text+0x26): undefined reference to `kunit_run_tests'
x86_64-linux-gnu-ld: drivers/base/test/property-entry-test.o: in function `pe_test_reference':
property-entry-test.c:(.text+0x275): undefined reference to `kunit_binary_assert_format'
x86_64-linux-gnu-ld: property-entry-test.c:(.text+0x2c4): undefined reference to `kunit_do_assertion'

and lots more ...

Caused by commit

  27f9d7e984d9 ("software node: introduce CONFIG_KUNIT_DRIVER_PE_TEST")

from the pm tree interacting with commit

  35c57fc3f8ea ("kunit: building kunit as a module breaks allmodconfig")

I have disabled CONFIG_KUNIT_DRIVER_PE_TEST for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2020-01-16  5:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16  5:57 Stephen Rothwell [this message]
2020-01-16 11:23 ` linux-next: build failure after merge of the kunit-next tree Alan Maguire
2020-01-16 23:27   ` Rafael J. Wysocki
  -- strict thread matches above, loose matches on Subject: below --
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-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=20200116165703.4e04be51@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=alan.maguire@oracle.com \
    --cc=brendanhiggins@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=skhan@linuxfoundation.org \
    /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).