From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Shuah Khan <skhan@linuxfoundation.org>,
Brendan Higgins <brendanhiggins@google.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warning after merge of the kunit-next tree
Date: Wed, 27 Apr 2022 16:19:01 +1000 [thread overview]
Message-ID: <20220427161901.6522f1cf@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
Hi all,
After merging the kunit-next tree, today's linux-next build (htmldocs)
produced this warning:
Documentation/dev-tools/kunit/api/test:9: include/kunit/test.h:318: WARNING: Inline interpreted text or phrase reference start-string without end-string.
Introduced by commit
9bf2eed995f9 ("kunit: add support for kunit_suites that reference init code")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-04-27 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 6:19 Stephen Rothwell [this message]
2022-07-04 23:17 ` linux-next: build warning after merge of the kunit-next tree Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2021-04-06 10:23 Stephen Rothwell
2021-04-06 17:32 ` Daniel Latypov
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=20220427161901.6522f1cf@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=brendanhiggins@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;
as well as URLs for NNTP newsgroup(s).