From: pierre Kuo <vichy.kuo@gmail.com>
To: perfbook@vger.kernel.org
Cc: Pierre Kuo <vichy.kuo@gmail.com>
Subject: [PATCH 2/2] SMPdesign: fix typo
Date: Thu, 2 Nov 2017 14:57:49 +0800 [thread overview]
Message-ID: <1509605869-8186-2-git-send-email-vichy.kuo@gmail.com> (raw)
In-Reply-To: <1509605869-8186-1-git-send-email-vichy.kuo@gmail.com>
From: Pierre Kuo <vichy.kuo@gmail.com>
In 6.5.1 Work-Queue Parallel Maze Solver, the line #4 and line #5 of
listing 6.13 seem describe the cell 't' instead of cell 'n'.
Signed-off-by: Pierre Kuo <vichy.kuo@gmail.com>
---
SMPdesign/beyond.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/SMPdesign/beyond.tex b/SMPdesign/beyond.tex
index 72862c5..88e2b31 100644
--- a/SMPdesign/beyond.tex
+++ b/SMPdesign/beyond.tex
@@ -141,8 +141,8 @@ Line~20 initializes for the next pass through the outer loop.
The pseudocode for \co{maze_try_visit_cell()} is shown on lines~1-12
of Listing~\ref{lst:SMPdesign:SEQ Helper Pseudocode}
(\path{maze.c}).
-Line~4 checks to see if cells \co{c} and \co{n} are adjacent and connected,
-while line~5 checks to see if cell \co{n} has not yet been visited.
+Line~4 checks to see if cells \co{c} and \co{t} are adjacent and connected,
+while line~5 checks to see if cell \co{t} has not yet been visited.
The \co{celladdr()} function returns the address of the specified cell.
If either check fails, line~6 returns failure.
Line~7 indicates the next cell, line~8 records this cell in the next
--
1.9.1
next prev parent reply other threads:[~2017-11-02 6:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 6:57 [PATCH 1/2] locking: fix typo pierre Kuo
2017-11-02 6:57 ` pierre Kuo [this message]
2017-11-02 22:51 ` Paul E. McKenney
2017-11-03 13:23 ` pierre kuo
2017-11-03 14:02 ` Paul E. McKenney
2017-11-03 14:41 ` pierre kuo
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=1509605869-8186-2-git-send-email-vichy.kuo@gmail.com \
--to=vichy.kuo@gmail.com \
--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.