All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org
Cc: SeongJae Park <sj38.park@gmail.com>, perfbook@vger.kernel.org
Subject: [PATCH 06/13] defer/rcuusage: Call paragraphs paragraphs, not sections
Date: Thu, 24 Nov 2022 10:57:56 -0800	[thread overview]
Message-ID: <20221124185803.8150-8-sj@kernel.org> (raw)
In-Reply-To: <20221124185803.8150-1-sj@kernel.org>

From: SeongJae Park <sj38.park@gmail.com>

Some sentences in rcuusage calls following paragraphs as sections.  Fix
it to minimize any confusion.

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 defer/rcuusage.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/defer/rcuusage.tex b/defer/rcuusage.tex
index 9da0e04c..8c45093f 100644
--- a/defer/rcuusage.tex
+++ b/defer/rcuusage.tex
@@ -946,7 +946,7 @@ There are, of course, limitations to RCU, including the fact that
 readers and updaters run concurrently, that low-priority RCU readers
 can block high-priority threads waiting for a grace period to elapse,
 and that grace-period latencies can extend for many milliseconds.
-These advantages and limitations are discussed in the following sections.
+These advantages and limitations are discussed in the following paragraphs.
 
 \paragraph{Performance}
 
@@ -1162,7 +1162,7 @@ systems are no longer uncommon and that a number of system calls (and
 thus any RCU read-side critical sections that they contain) complete
 within microseconds.
 
-In addition, as is discussed in the next section,
+In addition, as is discussed in the next paragraph,
 RCU read-side primitives are almost entirely deadlock-immune.
 
 
-- 
2.17.1


  parent reply	other threads:[~2022-11-24 18:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 18:57 [PATCH 00/13] Minor fixes for defer/ SeongJae Park
2022-11-24 18:57 ` [PATCH 01/13] defer/rcuintro: Clearly point the QSBR described section SeongJae Park
2022-11-24 18:57 ` [PATCH 02/13] defer/rcufundamental: Add non-breaking spaces SeongJae Park
2022-11-24 18:57 ` [PATCH 03/13] defer/rcuapi: Add missed unbreakable spaces SeongJae Park
2022-11-24 18:57 ` [PATCH 04/13] defer/rcuapi: Use \co{} for boolean return value SeongJae Park
2022-11-24 18:57 ` [PATCH 05/13] defer/seqlock: " SeongJae Park
2022-11-24 18:57 ` SeongJae Park [this message]
2022-11-24 18:57 ` [PATCH 07/13] defer/rcuusage: Provide the reference to synchronous RCU update-side primitives SeongJae Park
2022-11-24 18:57 ` [PATCH 08/13] defer/rcuusage: Add a missed unbreakable space SeongJae Park
2022-11-24 18:57 ` [PATCH 09/13] defer/rcuusage: Add missing '()' for 'rcu_dereference()' SeongJae Park
2022-11-24 18:58 ` [PATCH 10/13] defer/rcuusage: Fix wrong function name: s/timer_stop/nmi_stop/ SeongJae Park
2022-11-24 18:58 ` [PATCH 11/13] defer/rcurelated: Remove unopen closing parentheses SeongJae Park
2022-11-24 18:58 ` [PATCH 12/13] defer/whichtochoose: Fix a wrongly positioned unbreakable space SeongJae Park
2022-11-24 18:58 ` [PATCH 13/13] defer/whichtochoose: Remove an unnecessary space SeongJae Park
2022-11-24 20:48 ` [PATCH 00/13] Minor fixes for defer/ Paul E. McKenney
2022-11-24 20:56   ` SeongJae Park

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=20221124185803.8150-8-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=perfbook@vger.kernel.org \
    --cc=sj38.park@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.