From: SeongJae Park <sj38.park@gmail.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
SeongJae Park <sj38.park@gmail.com>,
perfbook@vger.kernel.org
Subject: Re: [PATCH -perfbook 2/7] formal/ppcmem: Use \qco{} as intended
Date: Sat, 29 Apr 2023 16:41:37 -0700 [thread overview]
Message-ID: <20230429234137.18677-1-sj@kernel.org> (raw)
In-Reply-To: <46c02030-ceca-2547-7b68-1e8642ae18fa@gmail.com>
On Sun, 30 Apr 2023 08:07:18 +0900 Akira Yokosawa <akiyks@gmail.com> wrote:
> Commit f87fadc4c8ea ("formal/ppcmem: Use \qco{} instead of ``\co{}''")
> did not use \qco{} in one of the hunks.
>
> Use \qco{} as intended.
Nice catch! Thank you for this fix!
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
> Cc: SeongJae Park <sj38.park@gmail.com>
Reviewed-by: SeongJae Park <sj38.park@gmail.com>
Thanks,
SJ
> ---
> formal/ppcmem.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/formal/ppcmem.tex b/formal/ppcmem.tex
> index 10526bca88ae..9d7704fa43d0 100644
> --- a/formal/ppcmem.tex
> +++ b/formal/ppcmem.tex
> @@ -99,7 +99,7 @@ exists @lnlbl[assert:b]
>
> \begin{fcvref}[ln:formal:PPCMEM Litmus Test]
> In the example, \clnref{type} identifies the type of system (\qco{ARM} or
> -\co{PPC}) and contains the title for the model.
> +\qco{PPC}) and contains the title for the model.
> \Clnref{altname} provides a place for an
> alternative name for the test, which you will usually want to leave
> blank as shown in the above example.
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2023-04-29 23:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 23:01 [PATCH -perfbook 0/7] Collection of minor fixes and updates Akira Yokosawa
2023-04-29 23:05 ` [PATCH -perfbook 1/7] formal/spinhint: Don't use \qco{} for long message Akira Yokosawa
2023-04-29 23:40 ` SeongJae Park
2023-04-29 23:07 ` [PATCH -perfbook 2/7] formal/ppcmem: Use \qco{} as intended Akira Yokosawa
2023-04-29 23:41 ` SeongJae Park [this message]
2023-04-30 0:26 ` Paul E. McKenney
2023-04-29 23:08 ` [PATCH -perfbook 3/7] Add acronyms of LKMM and KCSAN Akira Yokosawa
2023-04-29 23:13 ` [PATCH -perfbook 4/7] CodeSamples/count: Adjust coding style Akira Yokosawa
2023-04-29 23:16 ` [PATCH -perfbook 5/7] count: Adjust scaling factor of Listing 5.18 Akira Yokosawa
2023-04-29 23:22 ` [PATCH -perfbook 6/7] Tweak TOC width params Akira Yokosawa
2023-04-30 0:30 ` Paul E. McKenney
2023-04-29 23:23 ` [PATCH -perfbook 7/7] precheck.sh: Export LC_TIME Akira Yokosawa
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=20230429234137.18677-1-sj@kernel.org \
--to=sj38.park@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 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.