From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@kernel.org
Cc: akiyks@gmail.com, perfbook@vger.kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH] together/refcnt: Use \qco{} for code quoting
Date: Sun, 30 Apr 2023 08:44:11 -0700 [thread overview]
Message-ID: <20230430154411.28410-1-sj38.park@gmail.com> (raw)
\tco{} is for code in tabular environment, while \qco{} is for
non-breaking code with quotation marks. However, commit 0e96cb8283ca
("together/refcnt: Use \tco{} for code quoting") has mistakenly used
\tco{} for quoted code, by mistake. Fix it by replacing the \tco{} with
\qco{}.
Fixes: 0e96cb8283ca ("together/refcnt: Use \tco{} for code quoting")
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
together/refcnt.tex | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/together/refcnt.tex b/together/refcnt.tex
index 4abe1c60..11596f4e 100644
--- a/together/refcnt.tex
+++ b/together/refcnt.tex
@@ -467,15 +467,15 @@ as shown below.
\QuickQuiz{
Why can't the check for a zero reference count be
- made in a simple \tco{if} statement with an atomic
- increment in its \tco{then} clause?
+ made in a simple \qco{if} statement with an atomic
+ increment in its \qco{then} clause?
}\QuickQuizAnswer{
- Suppose that the \tco{if} condition completed, finding
+ Suppose that the \qco{if} condition completed, finding
the reference counter value equal to one.
Suppose that a release operation executes, decrementing
the reference counter to zero and therefore starting
cleanup operations.
- But now the \tco{then} clause can increment the counter
+ But now the \qco{then} clause can increment the counter
back to a value of one, allowing the object to be
used after it has been cleaned up.
--
2.17.1
next reply other threads:[~2023-04-30 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 15:44 SeongJae Park [this message]
2023-04-30 18:28 ` [PATCH] together/refcnt: Use \qco{} for code quoting 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=20230430154411.28410-1-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).