From: Akira Yokosawa <akiyks@gmail.com>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH -perfbook 0/4] Address potential widowing of headings
Date: Thu, 9 Dec 2021 09:03:50 +0900 [thread overview]
Message-ID: <7ab89db4-75eb-8e40-7601-a302cf1865d3@gmail.com> (raw)
In-Reply-To: <20211208235858.GA641268@paulmck-ThinkPad-P17-Gen-1>
On Wed, 8 Dec 2021 15:58:58 -0800, Paul E. McKenney wrote:
> On Thu, Dec 09, 2021 at 07:20:20AM +0900, Akira Yokosawa wrote:
[...]
>> So the diff below looks somewhat out of context, because the Quiz
>> part of QQ A.2 is "How could there be such a large gap between
>> successive consumer reads?".
>>
>> ----
>> @@ -175,7 +175,7 @@ seq & \multicolumn{1}{c}{time (seconds)} & delta~ & a & b & c \\
>> consumer reads?
>> See \path{timelocked.c} for full code.
>> }\QuickQuizAnswer{
>> - Here are possible scenarios:
>> + Here are a few of the errors:
>>
>> \begin{enumerate}
>> \item The consumer might be preempted for long time periods.
>> ----
>>
>> Thoughts?
>
> I changed this to "Here are a few reasons for such gaps:". Does
> that work for you?
Works for me!
Thanks, Akira
>
> Thanx, Paul
>
>> Thanks, Akira
[...]
next prev parent reply other threads:[~2021-12-09 0:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 7:37 [PATCH -perfbook 0/4] Address potential widowing of headings Akira Yokosawa
2021-12-08 7:39 ` [PATCH -perfbook 1/4] cleverefcheck.pl: Add test of listing next to heading Akira Yokosawa
2021-12-08 7:41 ` [PATCH -perfbook 2/4] cleverefcheck.pl: Add test of \begin{...} at head of QQA Akira Yokosawa
2021-12-08 7:49 ` [PATCH -perfbook 3/4] cleverefcheck.pl: Add test of \begin{...} next to epigraph Akira Yokosawa
2021-12-08 7:52 ` [PATCH -perfbook 4/4] treewide: Address potential widowing of headings Akira Yokosawa
2021-12-08 19:55 ` [PATCH -perfbook 0/4] " Paul E. McKenney
2021-12-08 22:20 ` Akira Yokosawa
2021-12-08 23:58 ` Paul E. McKenney
2021-12-09 0:03 ` Akira Yokosawa [this message]
2021-12-09 6:28 ` Zhouyi Zhou
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=7ab89db4-75eb-8e40-7601-a302cf1865d3@gmail.com \
--to=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 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.