Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: SeongJae Park <sj38.park@gmail.com>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 2/2] appendix/questions/after: Use \co{}
Date: Sun, 17 Dec 2023 09:41:17 -0800	[thread overview]
Message-ID: <20231217174117.6714-3-sj38.park@gmail.com> (raw)
In-Reply-To: <20231217174117.6714-1-sj38.park@gmail.com>

Some code snippets in after.tex are not enclosed with \co{}.  Enclose
those.

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

diff --git a/appendix/questions/after.tex b/appendix/questions/after.tex
index d6b0dfdf..768888ed 100644
--- a/appendix/questions/after.tex
+++ b/appendix/questions/after.tex
@@ -45,7 +45,7 @@ e.g., where time has appeared to go backwards.
 	Here are errors you might have found:
 
 	\begin{enumerate}
-	\item	Missing barrier() or volatile on tight loops.
+	\item	Missing \co{barrier()} or \co{volatile} on tight loops.
 	\item	Missing memory barriers on update side.
 	\item	Lack of synchronization between producer and consumer.
 	\end{enumerate}
-- 
2.17.1


  parent reply	other threads:[~2023-12-17 17:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17 17:41 [PATCH 0/2] appendix/questions: Trivial fixup SeongJae Park
2023-12-17 17:41 ` [PATCH 1/2] appendix/questions/after: Use \qco{} for quoting code SeongJae Park
2023-12-17 17:41 ` SeongJae Park [this message]
2023-12-17 20:50 ` [PATCH 0/2] appendix/questions: Trivial fixup 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=20231217174117.6714-3-sj38.park@gmail.com \
    --to=sj38.park@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