From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] memorder: Fix 'Non-Other-Multicopy Atomic?' row in summary table
Date: Fri, 6 Oct 2017 10:05:07 -0700 [thread overview]
Message-ID: <20171006170507.GG3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <dc43b2af-dc79-c0f0-6946-03a700a794a8@gmail.com>
On Fri, Oct 06, 2017 at 11:44:11PM +0900, Akira Yokosawa wrote:
> >From a28209de2cced673aa9a924cf7d038571886b6fd Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Fri, 6 Oct 2017 23:29:24 +0900
> Subject: [PATCH] memorder: Fix 'Non-Other-Multicopy Atomic?' row in summary table
>
> In commit c99a5407b2a6 ("memorder: Transpose table 'Summary of Memory
> Ordering'"), (PA-RISC), SPARC TSO, and x86 were marked "Y" in
> the "Non-Other-Multicopy Atomic?" row.
> The corresponding cells before the transposition had been blank.
>
> Remove those bogus "Y"s.
>
> Fixes: c99a5407b2a6
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Hmmm... I didn't proofread that transposition change very well, did I?
Anyway, applied and pushed, thank you!!!
Thanx, Paul
> ---
> memorder/memorder.tex | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/memorder/memorder.tex b/memorder/memorder.tex
> index ba54fee..eb498fb 100644
> --- a/memorder/memorder.tex
> +++ b/memorder/memorder.tex
> @@ -3744,7 +3744,7 @@ dependencies.
> & Y & Y & Y & Y & Y & Y & ~ & Y & Y & Y & ~ \\
> \cellcolor{white}
> & Non-Other-Multicopy Atomic?
> - & Y & ~ & Y & Y & Y & Y & ~ & Y & Y & Y & ~ \\
> + & Y & ~ & Y & Y & Y & ~ & ~ & Y & ~ & ~ & ~ \\
> & Non-Cache Coherent?
> & ~ & ~ & ~ & Y & ~ & ~ & ~ & ~ & ~ & ~ & ~ \\
> \cmidrule(r){1-2} \cmidrule{3-13}
> --
> 2.7.4
>
prev parent reply other threads:[~2017-10-06 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 14:44 [PATCH] memorder: Fix 'Non-Other-Multicopy Atomic?' row in summary table Akira Yokosawa
2017-10-06 17:05 ` Paul E. McKenney [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=20171006170507.GG3521@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akiyks@gmail.com \
--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