From: SeongJae Park <sj38.park@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
paulmck@kernel.org, perfbook@vger.kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: Re: [PATCH 1/5] debugging: Use \co{} for 'time' output examples
Date: Sat, 11 Feb 2023 09:03:15 -0800 [thread overview]
Message-ID: <20230211170315.8850-1-sj@kernel.org> (raw)
In-Reply-To: <6745658a-5dde-fe09-29dd-4428c34d75f3@gmail.com>
Hi Akira,
Sorry for late response.
On Mon, 6 Feb 2023 11:31:55 +0900 Akira Yokosawa <akiyks@gmail.com> wrote:
> Hi SeongJae,
>
> On Sun, 5 Feb 2023 10:21:24 -0800, SeongJae Park wrote:
> > From: SeongJae Park <sj38.park@gmail.com>
> >
> > A quick quiz answer in debugging.tex is wrapping 'time' example outputs
> > with `` and ''. Use \co{} instead.
> >
> > Signed-off-by: SeongJae Park <sj38.park@gmail.com>
> > ---
> > debugging/debugging.tex | 16 ++++++++--------
> > 1 file changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/debugging/debugging.tex b/debugging/debugging.tex
> > index 4568f90a..3104bb95 100644
> > --- a/debugging/debugging.tex
> > +++ b/debugging/debugging.tex
> > @@ -257,8 +257,8 @@ validation is just job for you.
> > consumed in system mode by a CPU-bound program?
> > \item Do you have a test case in which all three times
> > are zero?
> > - \item Do you have a test case in which the ``user'' and ``sys''
> > - times sum to more than the ``real'' time?
> > + \item Do you have a test case in which the \co{user} and \co{sys}
> > + times sum to more than the \co{real} time?
> > (This would of course be completely legitimate in
> > a multithreaded program.)
> > \item Do you have a set of tests cases in which one of the
> > @@ -267,7 +267,7 @@ validation is just job for you.
> > times uses more than ten seconds?
> > \item Do you have a set of test cases in which one of the
> > times has non-zero minutes?
> > - (For example, ``15m36.342s''.)
> > + (For example, \co{15m36.342s}.)
> > \item Do you have a set of test cases in which one of the
> > times has a seconds value of greater than 60?
> > \item Do you have a set of test cases in which one of the
> > @@ -279,21 +279,21 @@ validation is just job for you.
> > times has a positive minutes value but a negative
> > seconds value?
> > \item Do you have a set of test cases in which one of the
> > - times omits the ``m'' or the ``s''?
> > + times omits the \co{m} or the \co{s}?
> > \item Do you have a set of test cases in which one of the
> > times is non-numeric?
> > - (For example, ``Go Fish''.)
> > + (For example, \co{Go Fish}.)
>
> My preference is to enclose \co{Go Fish} by quotation marks.
> That is easier for me to see it as a string.
> There is a convenient macro \qco{} for this purpose. You can say:
>
> + (For example, \qco{Go Fish}.)
>
> > \item Do you have a set of test cases in which one of the
> > lines is omitted?
> > - (For example, where there is a ``real'' value and
> > - a ``sys'' value, but no ``user'' value.)
> > + (For example, where there is a \co{real} value and
> > + a \co{sys} value, but no \co{user} value.)
> > \item Do you have a set of test cases where one of the
> > lines is duplicated?
> > Or duplicated, but with a different time value for
> > the duplicate?
> > \item Do you have a set of test cases where a given line
> > has more than one time value?
> > - (For example, ``real 0m0.132s 0m0.008s''.)
> > + (For example, \co{real 0m0.132s 0m0.008s}.)
>
> Ditto.
>
> With them taken care of,
>
> Reviewed-by: Akira Yokosawa <akiyks@gmail.com>
Thank you for nice suggestions. I will revise as you suggested.
Thanks,
SJ
>
> Thanks, Akira
>
> > \item Do you have a set of test cases containing random
> > characters?
> > \item In all test cases involving invalid input, did you
next prev parent reply other threads:[~2023-02-11 17:03 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 [this message]
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 ` [PATCH 5/5] debugging/debugging: s/remainder of a section/following sections/ SeongJae Park
2023-02-06 3:01 ` 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=20230211170315.8850-1-sj@kernel.org \
--to=sj38.park@gmail.com \
--cc=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
--cc=sj@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.