public inbox for perfbook@vger.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH -perfbook 5/5] together/applyrcu: Use nbsp around one-letter variables in Section 13.5.10
Date: Tue, 7 Oct 2025 23:58:30 +0900	[thread overview]
Message-ID: <f4e32dfd-4fba-47ab-8cf2-7c4d0dd006df@gmail.com> (raw)
In-Reply-To: <50018985-d907-4028-b118-50c4c9fe894d@gmail.com>

Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
 together/applyrcu.tex | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/together/applyrcu.tex b/together/applyrcu.tex
index 455bf2a1..6004cb24 100644
--- a/together/applyrcu.tex
+++ b/together/applyrcu.tex
@@ -969,16 +969,16 @@ and transfer control to \clnref{unl:2}, which exits the RCU read-side critical
 section.
 \Clnref{init:a} initializes the element (abstracting away any required allocation),
 \clnref{xchg} atomically exchanges the pointer to this element with the global
-pointer \co{p}, returning the old value in \co{r1}.
+pointer~\co{p}, returning the old value in \co{r1}.
 If \clnref{if:2} determines that \co{r1} was non-\co{NULL}, then \clnref{sync}
 waits for any readers accessing the old element to finish and \clnref{free}
 emulates a \co{kfree()}.
-Either way, \co{r2} is set to the initial value of 1.
+Either way, \co{r2} is set to the initial value of~1.
 \end{fcvref}
 
 \begin{fcvref}[ln:formal:C-double-check-rcu-2:whole]
-\Clnrefrange{P1:b}{P1:e} operate in the same manner, but using element \co{b} instead
-of \co{a}.
+\Clnrefrange{P1:b}{P1:e} operate in the same manner, but using element~\co{b} instead
+of~\co{a}.
 
 \Clnref{loc} displays all variables to ease debugging of the litmus test.
 \Clnref{ex:1} verifies that both processes obtain an initialized value,
-- 
2.43.0



  parent reply	other threads:[~2025-10-07 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 14:48 [PATCH -perfbook 0/5] together/applyrcu: Final touches for recent updates Akira Yokosawa
2025-10-07 14:49 ` [PATCH -perfbook 1/5] CodeSamples/formal: Update rcu-test.dat for v6.17 Akira Yokosawa
2025-10-07 14:51 ` [PATCH -perfbook 2/5] together/applyrcu: Use \clnref{} and its friends in Section 13.5.9 Akira Yokosawa
2025-10-07 14:52 ` [PATCH -perfbook 3/5] together/applyrcu: Use nbsp around one-letter variables " Akira Yokosawa
2025-10-07 14:57 ` [PATCH -perfbook 4/5] together/applyrcu: Use \clnref{} and its friends in Section 13.5.10 Akira Yokosawa
2025-10-07 14:58 ` Akira Yokosawa [this message]
2025-10-07 15:12 ` [PATCH -perfbook 0/5] together/applyrcu: Final touches for recent updates 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=f4e32dfd-4fba-47ab-8cf2-7c4d0dd006df@gmail.com \
    --to=akiyks@gmail.com \
    --cc=paulmck@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox