From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>,
Leonardo Bras <leobras.c@gmail.com>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH -perfbook 4/4] toolsoftrade: Fix QQz macro in QQz series
Date: Tue, 14 Feb 2023 19:09:39 +0900 [thread overview]
Message-ID: <44251e0a-2617-361e-e61c-4dfefb5ae284@gmail.com> (raw)
In-Reply-To: <8f565979-bba0-bab1-7c8e-ebc76c2b4e65@gmail.com>
Final QQz in a QQz series start from "\QuickQuizE{" rather than
"\QuickQuizM{".
This typo resulted in an extra "," in the anchor box:
+----------------------+
| QQ 4.20, 4.21, 4.22, |
+----------------------+
Fix it.
Fixes: a39fae0f30a9 ("treewide: Use macros for consecutive quick quizzes")
Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
toolsoftrade/toolsoftrade.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
index fee34ae8a1df..8c9384049e75 100644
--- a/toolsoftrade/toolsoftrade.tex
+++ b/toolsoftrade/toolsoftrade.tex
@@ -947,7 +947,7 @@ in fact degraded by about 10\,\% from ideal.
sections are described in \cref{chp:Deferred Processing}.
}\QuickQuizEndM
%
-\QuickQuizM{
+\QuickQuizE{
The system used is a few years old, and new hardware should
be faster.
So why should anyone worry about reader-writer locks being slow?
--
2.25.1
next prev parent reply other threads:[~2023-02-14 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 10:03 [PATCH -perfbook 0/4] cpu/overheads: Make tables more consistent Akira Yokosawa
2023-02-14 10:05 ` [PATCH -perfbook 1/4] cpu: Improve layout and consistency of Tables 3.1, E.1, and E.2 Akira Yokosawa
2023-02-14 10:07 ` [PATCH -perfbook 2/4] cpu: Use 'on-core' rather than 'in-core' Akira Yokosawa
2023-02-14 10:08 ` [PATCH -perfbook 3/4] cpu: Add page reference to Table E.1 in QQz 3.8 Akira Yokosawa
2023-02-14 10:09 ` Akira Yokosawa [this message]
2023-02-14 23:13 ` [PATCH -perfbook 0/4] cpu/overheads: Make tables more consistent 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=44251e0a-2617-361e-e61c-4dfefb5ae284@gmail.com \
--to=akiyks@gmail.com \
--cc=leobras.c@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.