From: Zhouyi Zhou <zhouzhouyi@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org, "Paul E. McKenney" <paulmck@kernel.org>
Subject: Re: There is a line missing in the diagram Figure 10.18 and Figure E.7
Date: Mon, 15 Jan 2024 19:31:13 +0800 [thread overview]
Message-ID: <CAABZP2zCpcUayo2e1SEyZOXXu=6_25FOUs0rZN-eMreiV_0WrA@mail.gmail.com> (raw)
In-Reply-To: <e609d522-5652-4622-8e4b-f17c840055d3@gmail.com>
Thank Akira's guidance
On Mon, Jan 15, 2024 at 7:18 PM Akira Yokosawa <akiyks@gmail.com> wrote:
>
> Hi Zhouyi,
>
> On 2024/01/15 15:20, Zhouyi Zhou wrote:
> > Hi Paul and Akira,
> >
> > Our Chinese version editor Yunjing Li points out that there is a line
> > missing in Figure E.7, there should be 7, but Figure E.7 has only 6.
> >
> > Similarly, I found there should be 6 lines in Figure 10.18, but
> > actually it has only 5.
>
> There is a footnote on the uppermost three traces of Figure 10.18,
> which reads:
>
> You see only two traces? The dashed one is composed of two
> traces that differ only slightly, hence the irregular-looking
> dash pattern.
>
> It was added by commit 27dc9fbe7605 ("datastruct: Expand on the
> dash type of traces in Figure 10.19").
> Wouldn't it explain your observation?
Yes, the commit explains why FIgure 10.19 has 6 traces while Figure
E.7 has 7 traces. I will reflect the information to the editor and add
a footnote to Chapter 10.
Thanks, Zhouyi
>
> Thanks, Akira
>
> >
> > Although I am very glad to fix the above possible bugs, fixing them is
> > beyond my capability.
> >
> > Thanks, Zhouyi
> > Reported-by: Yunjing Li
> > Reported-by: Zhouyi Zhou <zhouzhouyi@gmail.com>
prev parent reply other threads:[~2024-01-15 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 6:20 There is a line missing in the diagram Figure 10.18 and Figure E.7 Zhouyi Zhou
2024-01-15 11:18 ` Akira Yokosawa
2024-01-15 11:31 ` Zhouyi Zhou [this message]
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='CAABZP2zCpcUayo2e1SEyZOXXu=6_25FOUs0rZN-eMreiV_0WrA@mail.gmail.com' \
--to=zhouzhouyi@gmail.com \
--cc=akiyks@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).