public inbox for perfbook@vger.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 07/12] formal/ppcmem: Use uppercase 'S' for Spin
Date: Sat,  8 Apr 2023 10:33:04 -0700	[thread overview]
Message-ID: <20230408173309.5543-8-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 using lowercase 's' for Spin, while
other sentences in other tex files are using the uppercase 'S'.
Consistently use uppercase 'S'.

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 9f584b15..62a45383 100644
--- a/formal/ppcmem.tex
+++ b/formal/ppcmem.tex
@@ -7,7 +7,7 @@
 %
 \epigraph{Jack of all trades, master of none.}{Unknown}
 
-Although Promela and spin allow you to verify pretty much any (smallish)
+Although Promela and Spin allow you to verify pretty much any (smallish)
 algorithm, their very generality can sometimes be a curse.
 For example, Promela does not understand memory models or any sort
 of reordering semantics.
@@ -403,7 +403,7 @@ These tools do have some intrinsic limitations:
 	running on small numbers of threads.
 	Larger examples result
 	in state-space explosion, just as with similar tools such as
-	Promela and spin.
+	Promela and Spin.
 \item	The full state-space search does not give any indication of how
 	each offending state was reached.
 	That said, once you realize that the state is in fact reachable,
-- 
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 ` SeongJae Park [this message]
2023-04-08 17:33 ` [PATCH 08/12] formal/ppcmem: " SeongJae Park
2023-04-08 17:33 ` [PATCH 09/12] formal/ppcmem: Add missed non-breakable spaces SeongJae Park
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-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox