From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org
Cc: SeongJae Park <sj38.park@gmail.com>, perfbook@vger.kernel.org
Subject: [PATCH 02/13] defer/rcufundamental: Add non-breaking spaces
Date: Thu, 24 Nov 2022 10:57:52 -0800 [thread overview]
Message-ID: <20221124185803.8150-4-sj@kernel.org> (raw)
In-Reply-To: <20221124185803.8150-1-sj@kernel.org>
From: SeongJae Park <sj38.park@gmail.com>
Linked list example in rcufundamental.tex misses non-breaking spaces
between 'and' and a data item. Add it for better compilation of the
book.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
defer/rcufundamental.tex | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/defer/rcufundamental.tex b/defer/rcufundamental.tex
index 39b2f7ff..5e7d6675 100644
--- a/defer/rcufundamental.tex
+++ b/defer/rcufundamental.tex
@@ -153,7 +153,7 @@ structures without disrupting concurrent readers.
items from a linked list while a reader is iterating over that
same list.
Specifically, suppose that a list initially contains elements
- A, B, and C, and that an updater removes element A and then
+ A, B, and~C, and that an updater removes element A and then
adds a new element D at the end of the list.
The reader might well see \{A, B, C, D\}, when that sequence of
elements never actually ever existed!
@@ -163,8 +163,8 @@ structures without disrupting concurrent readers.
In the universe where an iterating reader is only required to
traverse elements that were present throughout the full duration
of the iteration.
- In the example, that would be elements B and C\@.
- Because elements A and D were each present for only part of the
+ In the example, that would be elements B and~C\@.
+ Because elements A and~D were each present for only part of the
iteration, the reader is permitted to iterate over them, but not
obliged to.
Note that this supports the common case where the reader is simply
--
2.17.1
next prev 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 ` SeongJae Park [this message]
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 ` [PATCH 06/13] defer/rcuusage: Call paragraphs paragraphs, not sections SeongJae Park
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-4-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox