All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: akiyks@gmail.com, perfbook@vger.kernel.org,
	SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH v3 02/17] formal/spinhint: Add missing NBSPs
Date: Wed, 28 Sep 2016 06:56:26 +0900	[thread overview]
Message-ID: <20160927215641.7330-2-sj38.park@gmail.com> (raw)
In-Reply-To: <20160927215641.7330-1-sj38.park@gmail.com>

This commit adds missing non-breakable spaces.

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

diff --git a/formal/spinhint.tex b/formal/spinhint.tex
index 10f6263..7787ed8 100644
--- a/formal/spinhint.tex
+++ b/formal/spinhint.tex
@@ -738,7 +738,7 @@ havelock array entry on line~26, starts the current locker on
 line~27, and advances to the next locker on line~28.
 Once all locker processes are spawned, the do-od loop
 moves to line~29, which checks the assertion.
-Lines 30 and 31 initialize the control variables,
+Lines~30 and~31 initialize the control variables,
 lines~32-40 atomically sum the havelock array entries,
 line~41 is the assertion, and line~42 exits the loop.

@@ -1009,7 +1009,7 @@ of the pair and sums them.
 The atomic block consists of a single do-od statement.
 This do-od statement (spanning lines~3-12) is unusual in that
 it contains two unconditional
-branches with guards on lines 4 and 8, which causes Promela to
+branches with guards on lines~4 and~8, which causes Promela to
 non-deterministically choose one of the two (but again, the full
 state-space search causes Promela to eventually make all possible
 choices in each applicable situation).
@@ -1107,7 +1107,7 @@ re-invoke \co{sum_unordered} if the fastpath is potentially
 usable.

 Lines~28-40 execute the slowpath code if need be, with
-lines 30 and 38 acquiring and releasing the update-side lock,
+lines~30 and~38 acquiring and releasing the update-side lock,
 lines~31-33 flipping the index, and lines~34-37 waiting for
 all pre-existing readers to complete.

@@ -1374,7 +1374,7 @@ Is QRCU really correct?
 We have a Promela-based mechanical proof and a by-hand proof that both
 say that it is.
 However, a recent paper by Alglave et al.~\cite{JadeAlglave2013-cav}
-says otherwise (see Section 5.1 of the paper at the bottom of page 12).
+says otherwise (see Section~5.1 of the paper at the bottom of page~12).
 Which is it?

 I do not know, as I never have been able to track down the code in which
-- 
2.10.0


  reply	other threads:[~2016-09-27 21:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 21:56 [PATCH v3 01/17] formal: Rearrange promela sample code location SeongJae Park
2016-09-27 21:56 ` SeongJae Park [this message]
2016-09-27 21:56 ` [PATCH v3 03/17] formal/spinhint: Fix typos SeongJae Park
2016-09-27 21:56 ` [PATCH v3 04/17] formal/spinhint: Use \path{} for file name quotation SeongJae Park
2016-09-27 21:56 ` [PATCH v3 05/17] formal/spinhint: Use \co{} for variable quotation consistently SeongJae Park
2016-09-27 21:56 ` [PATCH v3 06/17] formal/spinhint: Reference figure SeongJae Park
2016-09-27 21:56 ` [PATCH v3 07/17] formal/dyntickrcu: Add missing NBSPs SeongJae Park
2016-09-27 21:56 ` [PATCH v3 08/17] formal/dyntickrcu: Append `()` to function name quotations SeongJae Park
2016-09-27 21:56 ` [PATCH v3 09/17] formal/dyntickrcu: Fix typos SeongJae Park
2016-09-27 21:56 ` [PATCH v3 10/17] formal/dyntickrcu: Fix wrong line number quotation SeongJae Park
2016-09-27 21:56 ` [PATCH v3 11/17] formal/dyntickrcu: Fix wrong function name quotation SeongJae Park
2016-09-27 21:56 ` [PATCH v3 12/17] formal/ppcmem: Fix typo for \co{} SeongJae Park
2016-09-27 21:56 ` [PATCH v3 13/17] formal/ppcmem: Use \co{} for instruction quotation SeongJae Park
2016-09-27 21:56 ` [PATCH v3 14/17] formal/ppcmem: Use P0 instead of thread 1 SeongJae Park
2016-09-27 21:56 ` [PATCH v3 15/17] formal/ppcmem: Substitute `paper` with `chapter` SeongJae Park
2016-09-27 21:56 ` [PATCH v3 16/17] formal/ppcmem: Polish a sentence by removing unnecessary conjunction SeongJae Park
2016-09-27 21:56 ` [PATCH v3 17/17] formal/dyntickrcu: Adjust font size of sample code SeongJae Park
2016-09-27 23:19 ` [PATCH v3 01/17] formal: Rearrange promela sample code location 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=20160927215641.7330-2-sj38.park@gmail.com \
    --to=sj38.park@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=perfbook@vger.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 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.