From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] toolsoftrade: Trivial typo fixes
Date: Thu, 29 Dec 2016 08:31:41 -0800 [thread overview]
Message-ID: <20161229163141.GG3742@linux.vnet.ibm.com> (raw)
In-Reply-To: <692c6e8e-07e0-2c8c-daba-8961890e4086@gmail.com>
On Thu, Dec 29, 2016 at 08:16:16PM +0900, Akira Yokosawa wrote:
> >From 898b1101cf7f88f42b57f88d7539c6a579f3106a Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Thu, 29 Dec 2016 19:42:34 +0900
> Subject: [PATCH] toolsoftrade: Trivial typo fixes
>
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Applied and pushed, thank you!
Thanx, Paul
> ---
> toolsoftrade/toolsoftrade.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
> index f76b250..1946599 100644
> --- a/toolsoftrade/toolsoftrade.tex
> +++ b/toolsoftrade/toolsoftrade.tex
> @@ -1280,7 +1280,7 @@ The C11 standard added atomic operations,
> including loads (\co{atomic_load()}),
> stores (\co{atomic_store()}),
> memory barriers (\co{atomic_thread_fence()} and
> -\co{atomic_signal_fence()}), and read-modified-write atomics.
> +\co{atomic_signal_fence()}), and read-modify-write atomics.
> The read-modify-write atomics include
> \co{atomic_fetch_add()},
> \co{atomic_fetch_sub()},
> @@ -1849,7 +1849,7 @@ shown in
> Section~\ref{sec:toolsoftrade:Atomic Operations}
> to that of per-CPU (or per-thread) variables
> (see Section~\ref{sec:toolsoftrade:Per-CPU Variables}),
> -as well as to conventional increment (as in ``counter++'').
> +as well as to conventional increment (as in ``\co{counter++}'').
>
> % \emph{@@@ need parable on cache thrashing.}
>
> --
> 2.7.4
>
prev parent reply other threads:[~2016-12-29 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 11:16 [PATCH] toolsoftrade: Trivial typo fixes Akira Yokosawa
2016-12-29 16:31 ` 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=20161229163141.GG3742@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