public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Joel Fernandes <joel@joelfernandes.org>,
	Josh Triplett <josh@joshtriplett.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Randy Dunlap <rdunlap@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, rcu@vger.kernel.org
Subject: Re: [PATCH 3/4] docs: RCU: Requirements.rst: fix a list block
Date: Tue, 6 Oct 2020 09:36:15 -0700	[thread overview]
Message-ID: <20201006163615.GL29330@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <9f666389cd803b392bf422d31e50c5f9f8c9474c.1601990386.git.mchehab+huawei@kernel.org>

On Tue, Oct 06, 2020 at 03:21:32PM +0200, Mauro Carvalho Chehab wrote:
> 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.
> 
> Fixes: 2a721e5f0b2c ("docs: Update RCU's hotplug requirements with a bit about design")
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>

Applied, thank you!

							Thanx, Paul

> ---
>  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 98557fee90cc..9f362827133a 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.26.2
> 

  reply	other threads:[~2020-10-06 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06 13:21 [PATCH 0/4] linu-next next-20201006 document build fixes Mauro Carvalho Chehab
2020-10-06 13:21 ` [PATCH 1/4] docs: infrastructure.rst: exclude device_link_state from device.h Mauro Carvalho Chehab
2020-10-06 13:21 ` [PATCH 2/4] docs: zh_CN: amu.rst: fix document title markup Mauro Carvalho Chehab
2020-10-06 13:21 ` [PATCH 3/4] docs: RCU: Requirements.rst: fix a list block Mauro Carvalho Chehab
2020-10-06 16:36   ` Paul E. McKenney [this message]
2020-10-06 13:21 ` [PATCH 4/4] firmware_loader: fix a kernel-doc markup Mauro Carvalho Chehab

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=20201006163615.GL29330@paulmck-ThinkPad-P72 \
    --to=paulmck@kernel.org \
    --cc=corbet@lwn.net \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rcu@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=will@kernel.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