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 2/2] together/seqlock: Use term 'sequence lock' consistently
Date: Sat, 29 Apr 2023 10:02:26 -0700	[thread overview]
Message-ID: <20230429170226.3640-3-sj@kernel.org> (raw)
In-Reply-To: <20230429170226.3640-1-sj@kernel.org>

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

A sentence in seqlock.tex is calling sequence locks as sequence
counters, while all other sentences in the file is calling those
sequence locks.  Use the term consistently.

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 together/seqlock.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/together/seqlock.tex b/together/seqlock.tex
index 5fd31d83..b77b5184 100644
--- a/together/seqlock.tex
+++ b/together/seqlock.tex
@@ -8,7 +8,7 @@
 \epigraph{The girl who can't dance says the band can't play.}
 	 {Yiddish proverb}
 
-This section looks at some special uses of sequence counters.
+This section looks at some special uses of sequence locks.
 
 \subsection{Dueling Sequence Locks}
 \label{sec:together:Dueling Sequence Locks}
-- 
2.17.1


      parent reply	other threads:[~2023-04-29 17:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-29 17:02 [PATCH 0/2] together: Minor fixups SeongJae Park
2023-04-29 17:02 ` [PATCH 1/2] together/refcnt: Use \tco{} for code quoting SeongJae Park
2023-04-29 22:20   ` Akira Yokosawa
2023-04-29 23:38     ` SeongJae Park
2023-04-30  3:12       ` Akira Yokosawa
2023-04-30  3:17         ` Paul E. McKenney
2023-04-30 21:07           ` SeongJae Park
2023-04-30 22:51             ` Paul E. McKenney
2023-04-29 17:02 ` SeongJae Park [this message]

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=20230429170226.3640-3-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.