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 09/12] formal/ppcmem: Add missed non-breakable spaces
Date: Sat,  8 Apr 2023 10:33:06 -0700	[thread overview]
Message-ID: <20230408173309.5543-10-sj@kernel.org> (raw)
In-Reply-To: <20230408173309.5543-1-sj@kernel.org>

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

A few sentences in ppcmem.tex are missing non-breakable spaces.  Add
those.

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

diff --git a/formal/ppcmem.tex b/formal/ppcmem.tex
index 9acd4dba..c3f5f943 100644
--- a/formal/ppcmem.tex
+++ b/formal/ppcmem.tex
@@ -110,13 +110,13 @@ Comments can be inserted between
 each is of the form
 \co{P:R=V}, where \co{P} is the process identifier, \co{R} is the register
 identifier, and \co{V} is the value.
-For example, process 0's register r3 initially contains the value~2.
+For example, process~0's register r3 initially contains the value~2.
 If the value is a variable (\co{x}, \co{y}, or \co{z} in the example)
 then the register is initialized to the address of the variable.
 It is also possible to initialize the contents of variables, for example,
 \co{x=1} initializes the value of \co{x} to~1.
 Uninitialized variables default to the value zero, so that in the
-example, \co{x}, \co{y}, and \co{z} are all initially zero.
+example, \co{x}, \co{y}, and~\co{z} are all initially zero.
 
 \Clnref{procid} provides identifiers for the two processes, so that
 the \co{0:r3=2} on \clnref{init:0} could instead have been written
-- 
2.17.1


  parent reply	other threads:[~2023-04-08 17:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-08 17:32 [PATCH 00/12] formal: Trivial fixups SeongJae Park
2023-04-08 17:32 ` [PATCH 01/12] formal/formal: Drop cppmem from 'Special-Purpose State-Space Search' section explanation SeongJae Park
2023-04-08 17:32 ` [PATCH 02/12] formal/spinhint: Use \qco{} instead of ``\co{}'' SeongJae Park
2023-04-08 17:33 ` [PATCH 03/12] formal/spinhint: Enclose example code snippets with \co{} SeongJae Park
2023-04-08 17:33 ` [PATCH 04/12] formal/spinhint: Do not call 2013 paper as recent SeongJae Park
2023-04-08 17:33 ` [PATCH 05/12] formal/dyntickrcu: Quote 'trail' file consistently SeongJae Park
2023-04-08 17:33 ` [PATCH 06/12] formal/dyntickrcu: Use \qco{} instead of ``\co{}'' SeongJae Park
2023-04-08 17:33 ` [PATCH 07/12] formal/ppcmem: Use uppercase 'S' for Spin SeongJae Park
2023-04-08 17:33 ` [PATCH 08/12] formal/ppcmem: Use \qco{} instead of ``\co{}'' SeongJae Park
2023-04-08 17:33 ` SeongJae Park [this message]
2023-04-08 17:33 ` [PATCH 10/12] formal/ppcmem: Enclose example code snippets with \co{} SeongJae Park
2023-04-08 17:33 ` [PATCH 11/12] formal/ppcmem: s/powerpc/PowerPC/ on sentences SeongJae Park
2023-04-08 17:33 ` [PATCH 12/12] formal/ppcmem: Fix label name for Fail1: SeongJae Park
2023-04-10  2:42 ` [PATCH 00/12] formal: Trivial fixups 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=20230408173309.5543-10-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.