From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Shuah Khan <skhan@linuxfoundation.org>,
Brendan Higgins <brendanhiggins@google.com>
Cc: Daniel Latypov <dlatypov@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the kunit-fixes tree
Date: Fri, 25 Jun 2021 19:52:32 +1000 [thread overview]
Message-ID: <20210625195232.3a307e53@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
Hi all,
After merging the kunit-fixes tree, today's linux-next build (powerpc
allyesconfig) failed like this:
lib/kunit/executor.c:26:1: error: expected identifier or '(' before '+' token
26 | +kunit_filter_subsuite(struct kunit_suite * const * const subsuite,
| ^
lib/kunit/executor.c: At top level:
lib/kunit/executor.c:140:10: fatal error: executor_test.c: No such file or directory
140 | #include "executor_test.c"
| ^~~~~~~~~~~~~~~~~
Caused by commit
c9d80ffc5a0a ("kunit: add unit test for filtering suites by names")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-06-25 9:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 9:52 Stephen Rothwell [this message]
2021-06-25 17:53 ` linux-next: build failure after merge of the kunit-fixes tree Daniel Latypov
2021-06-25 18:12 ` Shuah Khan
2021-06-25 18:46 ` Brendan Higgins
-- 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
2024-08-05 23:18 Stephen Rothwell
2024-08-06 2:06 ` David Gow
2024-08-06 19:20 ` Shuah Khan
2024-08-06 22:29 ` Shuah Khan
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=20210625195232.3a307e53@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brendanhiggins@google.com \
--cc=dlatypov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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