From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 5/5] debugging/debugging: s/remainder of a section/following sections/
Date: Sun, 5 Feb 2023 10:21:28 -0800 [thread overview]
Message-ID: <20230205182128.19044-6-sj@kernel.org> (raw)
In-Reply-To: <20230205182128.19044-1-sj@kernel.org>
From: SeongJae Park <sj38.park@gmail.com>
A sectence in 'Microbenchmarking' section is mentioning the remainder of
the section will look at ways for dealing with conflicts in measurement
error advices, but those are not dealt in the remainder of the section
but its following sections. Fix the sentence.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
debugging/debugging.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debugging/debugging.tex b/debugging/debugging.tex
index 53c7fb94..225a4184 100644
--- a/debugging/debugging.tex
+++ b/debugging/debugging.tex
@@ -2302,7 +2302,7 @@ to creep in, including:
The first and fourth sources of interference provide conflicting advice,
which is one sign that we are living in the real world.
-The remainder of this section looks at ways of resolving this conflict.
+The following sections look at ways of resolving this conflict.
\QuickQuiz{
But what about other sources of error, for example, due to
--
2.17.1
next prev parent reply other threads:[~2023-02-05 18:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 18:21 [PATCH 0/5] debugging: Trivial fixups SeongJae Park
2023-02-05 18:21 ` [PATCH 1/5] debugging: Use \co{} for 'time' output examples SeongJae Park
2023-02-06 2:31 ` Akira Yokosawa
2023-02-11 17:03 ` SeongJae Park
2023-02-05 18:21 ` [PATCH 2/5] debugging: Use \co{} for 'git' and 'Fixes:' SeongJae Park
2023-02-06 2:38 ` Akira Yokosawa
2023-02-11 17:04 ` SeongJae Park
2023-02-05 18:21 ` [PATCH 3/5] debugging: Use \co{} for rcutorture SeongJae Park
2023-02-06 2:48 ` Akira Yokosawa
2023-02-06 17:40 ` Paul E. McKenney
2023-02-05 18:21 ` [PATCH 4/5] debugging: Remove unnecessary space in a sentence SeongJae Park
2023-02-06 2:53 ` Akira Yokosawa
2023-02-11 17:05 ` SeongJae Park
2023-02-05 18:21 ` SeongJae Park [this message]
2023-02-06 3:01 ` [PATCH 5/5] debugging/debugging: s/remainder of a section/following sections/ Akira Yokosawa
2023-02-06 17:33 ` Paul E. McKenney
2023-02-11 17:06 ` SeongJae Park
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=20230205182128.19044-6-sj@kernel.org \
--to=sj@kernel.org \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.com \
/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