From: paulmck@kernel.org
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
mingo@kernel.org, jiangshanlai@gmail.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
fweisbec@gmail.com, oleg@redhat.com, joel@joelfernandes.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"Paul E . McKenney" <paulmck@kernel.org>
Subject: [PATCH tip/core/rcu 3/4] docs: RCU: Requirements.rst: Fix a list block
Date: Thu, 5 Nov 2020 15:05:09 -0800 [thread overview]
Message-ID: <20201105230510.18660-3-paulmck@kernel.org> (raw)
In-Reply-To: <20201105230444.GA18574@paulmck-ThinkPad-P72>
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
As warned by Sphinx:
.../Documentation/RCU/Design/Requirements/Requirements.rst:1959: WARNING: Unexpected indentation.
The list block is missing a space before it, making Sphinx to get
it wrong. This commit therefore adds the missing space characters.
Fixes: 2a721e5f0b2c ("docs: Update RCU's hotplug requirements with a bit about design")
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
---
Documentation/RCU/Design/Requirements/Requirements.rst | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/RCU/Design/Requirements/Requirements.rst b/Documentation/RCU/Design/Requirements/Requirements.rst
index 98557fe..9f36282 100644
--- a/Documentation/RCU/Design/Requirements/Requirements.rst
+++ b/Documentation/RCU/Design/Requirements/Requirements.rst
@@ -1954,6 +1954,7 @@ offline CPUs. However, as a debugging measure, the FQS loop does splat
if offline CPUs block an RCU grace period for too long.
An offline CPU's quiescent state will be reported either:
+
1. As the CPU goes offline using RCU's hotplug notifier (``rcu_report_dead()``).
2. When grace period initialization (``rcu_gp_init()``) detects a
race either with CPU offlining or with a task unblocking on a leaf
--
2.9.5
next prev parent reply other threads:[~2020-11-05 23:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 23:04 [PATCH tip/core/rcu 0/4] Documentations updates for v5.11 Paul E. McKenney
2020-11-05 23:05 ` [PATCH tip/core/rcu 1/4] doc: Present the role of READ_ONCE() paulmck
2020-11-09 12:21 ` Peter Zijlstra
2020-11-09 16:20 ` Paul E. McKenney
2020-11-05 23:05 ` [PATCH tip/core/rcu 2/4] docs: Update RCU's hotplug requirements with a bit about design paulmck
2020-11-09 12:23 ` Peter Zijlstra
2020-11-09 16:24 ` Paul E. McKenney
2020-11-09 17:14 ` Peter Zijlstra
2020-11-10 20:33 ` Joel Fernandes
2020-11-11 0:20 ` Paul E. McKenney
2020-11-05 23:05 ` paulmck [this message]
2020-11-05 23:05 ` [PATCH tip/core/rcu 4/4] docs/rcu: Update the call_rcu() API paulmck
2020-11-09 12:24 ` Peter Zijlstra
2020-11-10 1:20 ` Paul E. McKenney
2020-11-10 9:25 ` Peter Zijlstra
2020-11-10 14:37 ` 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=20201105230510.18660-3-paulmck@kernel.org \
--to=paulmck@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mchehab+huawei@kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).