From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Paul E. McKenney" <paulmck@kernel•org>
Cc: Zhen Lei <thunder.leizhen@huawei•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build warnings after merge of the rcu tree
Date: Wed, 23 Nov 2022 16:32:55 +1100 [thread overview]
Message-ID: <20221123163255.48653674@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 662 bytes --]
Hi all,
After merging the rcu tree, today's linux-next build (htmldocs) produced
these warnings:
Documentation/RCU/stallwarn.rst:401: WARNING: Literal block expected; none found.
Documentation/RCU/stallwarn.rst:428: WARNING: Literal block expected; none found.
Documentation/RCU/stallwarn.rst:445: WARNING: Literal block expected; none found.
Documentation/RCU/stallwarn.rst:459: WARNING: Literal block expected; none found.
Documentation/RCU/stallwarn.rst:468: WARNING: Literal block expected; none found.
Introduced by commit
3d2788ba4573 ("doc: Document CONFIG_RCU_CPU_STALL_CPUTIME=y stall information")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-11-23 5:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 5:32 Stephen Rothwell [this message]
2022-11-23 8:19 ` linux-next: build warnings after merge of the rcu tree Leizhen (ThunderTown)
2022-11-23 14:27 ` Paul E. McKenney
-- strict thread matches above, loose matches on Subject: below --
2024-08-09 4:26 Stephen Rothwell
2024-08-09 6:18 ` Z qiang
2020-11-26 6:44 Stephen Rothwell
2020-11-26 15:12 ` Paul E. McKenney
2020-11-26 17:28 ` Uladzislau Rezki
2020-11-10 6:59 Stephen Rothwell
2020-11-10 15:21 ` Paul E. McKenney
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=20221123163255.48653674@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paulmck@kernel$(echo .)org \
--cc=thunder.leizhen@huawei$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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