From: Zhouyi Zhou <zhouzhouyi@gmail.com>
To: perfbook@vger.kernel.org, luyang.co@gmail.com,
paulmck@kernel.org, akiyks@gmail.com
Cc: Zhouyi Zhou <zhouzhouyi@gmail.com>
Subject: [PATCH -perfbook] memorder: fix a line number reference error
Date: Fri, 14 Oct 2022 13:55:43 +0800 [thread overview]
Message-ID: <20221014055543.8214-1-zhouzhouyi@gmail.com> (raw)
In section 15.2.3, "Listing 15.10 shows how to make this work
reliably on pre-v4.15 Linux kernels running on DEC Alpha, by
replacing line 19' READ_ONCE() with lockless_dereference()"
line 19 should be line 18.
Signed-off-by: Zhouyi Zhou <zhouzhouyi@gmail.com>
---
Hi Paul
I like Chapter 15 very much as well as other chapters,
I used to read one paragraph a day when I am travelling ;-)
I think there is a small line number reference error in chapter
15.2.3, ignore me if it is not a error.
Many Thanks
Zhouyi
--
memorder/memorder.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/memorder/memorder.tex b/memorder/memorder.tex
index c350758d..1839e276 100644
--- a/memorder/memorder.tex
+++ b/memorder/memorder.tex
@@ -1279,7 +1279,7 @@ exists (1:r2=x0 /\ 1:r3=1)
% \path{C-MP+o-wmb-o+ld-addr-o.litmus} available at commit bc4b1c3f3b35
% ("styleguide: Loosen restriction on comment in litmus test")
shows how to make this work reliably on pre-v4.15 Linux kernels running on
-DEC Alpha, by replacing \clnref{read}'s \co{READ_ONCE()} with
+DEC Alpha, by replacing \clnref{deref}'s \co{READ_ONCE()} with
\apikh{lockless_dereference()},\footnote{
Note that \co{lockless_dereference()} is not needed on v4.15 and
later, and therefore is not available in these later Linux kernels.
--
2.34.1
next reply other threads:[~2022-10-14 5:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 5:55 Zhouyi Zhou [this message]
2022-10-14 9:42 ` [PATCH -perfbook] memorder: fix a line number reference error Akira Yokosawa
2022-10-14 10:44 ` [PATCH -perfbook v2] " Akira Yokosawa
2022-10-14 3:19 ` Zhouyi Zhou
2022-10-14 12:27 ` 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=20221014055543.8214-1-zhouzhouyi@gmail.com \
--to=zhouzhouyi@gmail.com \
--cc=akiyks@gmail.com \
--cc=luyang.co@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).