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 3/6] toolsoftrade: Use nbsp in front of single letter variable
Date: Sat, 7 Mar 2020 07:50:05 +0900 [thread overview]
Message-ID: <a5d41ae8-e6f3-a149-1bd4-f35ae48e39bf@gmail.com> (raw)
In-Reply-To: <0a98646c-eb33-a27c-b974-ff38b8652a44@gmail.com>
From 415ec82df62f29b0901b124c6991f05117432835 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@gmail.com>
Date: Fri, 6 Mar 2020 00:18:34 +0900
Subject: [PATCH 3/6] toolsoftrade: Use nbsp in front of single letter variable
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
toolsoftrade/toolsoftrade.tex | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
index 01529a0c..79d6c2cd 100644
--- a/toolsoftrade/toolsoftrade.tex
+++ b/toolsoftrade/toolsoftrade.tex
@@ -681,7 +681,7 @@ values of \co{x} stored by \co{lock_writer()}.
\QuickQuiz{}
Wait a minute here!!!
Listing~\ref{lst:toolsoftrade:Demonstration of Same Exclusive Lock}
- didn't initialize shared variable \co{x},
+ didn't initialize shared variable~\co{x},
so why does it need to be initialized in
Listing~\ref{lst:toolsoftrade:Demonstration of Different Exclusive Locks}?
\QuickQuizAnswer{
@@ -689,11 +689,10 @@ values of \co{x} stored by \co{lock_writer()}.
Listing~\ref{lst:toolsoftrade:Demonstration of Exclusive Locks}.
Because the code in
Listing~\ref{lst:toolsoftrade:Demonstration of Same Exclusive Lock}
- ran first, it could rely on the compile-time initialization of
- \co{x}.
+ ran first, it could rely on the compile-time initialization of~\co{x}.
The code in
Listing~\ref{lst:toolsoftrade:Demonstration of Different Exclusive Locks}
- ran next, so it had to re-initialize \co{x}.
+ ran next, so it had to re-initialize~\co{x}.
} \QuickQuizEnd
Although there is quite a bit more to POSIX exclusive locking, these
--
2.17.1
next prev parent reply other threads:[~2020-03-06 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 22:46 [PATCH 0/6] Improve page/column breaks in Appendix E Akira Yokosawa
2020-03-06 22:47 ` [PATCH 1/6] qqz.sty: " Akira Yokosawa
2020-03-06 22:49 ` [PATCH 2/6] qqz.sty: Fix position of \goodbreak for accuracy of hyperlinks Akira Yokosawa
2020-03-06 22:50 ` Akira Yokosawa [this message]
2020-03-06 22:51 ` [PATCH 4/6] debugging: Add opening sentence in Answer to QQZ 11.2 Akira Yokosawa
2020-03-06 22:52 ` [PATCH 5/6] defer/rcuusage: Reverse nesting of fcvref and enumerate envs Akira Yokosawa
2020-03-06 22:53 ` [PATCH 6/6] SMPdesign/partexercises: Move figure env next to first paragraph in QQA Akira Yokosawa
2020-03-07 1:29 ` [PATCH 0/6] Improve page/column breaks in Appendix E 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=a5d41ae8-e6f3-a149-1bd4-f35ae48e39bf@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 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.