From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: SeongJae Park <sj38.park@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] advsync: fix trivial typos
Date: Mon, 25 Apr 2016 18:39:06 -0700 [thread overview]
Message-ID: <20160426013906.GX3874@linux.vnet.ibm.com> (raw)
In-Reply-To: <1461633750-17992-1-git-send-email-sj38.park@gmail.com>
On Tue, Apr 26, 2016 at 10:22:30AM +0900, SeongJae Park wrote:
> Earlier two commits to advsync/memorybarriers.tex file, commit
> 8de1474e3282 ("Add larger multiple-value-write scenario") and commit
> 514f21cd4156 ("Add caveats to the Software Logic Analyzer") has made few
> trivial typos. This commit fixes them.
>
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Good eyes! Queued and pushed.
Thanx, Paul
> ---
> advsync/memorybarriers.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/advsync/memorybarriers.tex b/advsync/memorybarriers.tex
> index cc39d2d..a0ef76d 100644
> --- a/advsync/memorybarriers.tex
> +++ b/advsync/memorybarriers.tex
> @@ -363,7 +363,7 @@ consistent with the increase in number of CPUs.
> The remaining 15 columns in the table record the values most recently
> observed by the corresponding CPU at each point in time, with changes
> in value marked by italics and parentheses.
> -Again, CPU 0 coordinates the test, so does not record any values.
> +Again, CPU~0 coordinates the test, so does not record any values.
>
> \begin{table*}[htbp]
> \scriptsize
> @@ -508,7 +508,7 @@ We have entered a regime where we must bid a fond farewell to
> comfortable intuitions about values of variables and the passage of time.
> This is the regime where memory barriers are needed.
>
> -All that aside, is is important to remember the lessons from
> +All that aside, it is important to remember the lessons from
> Chapters~\ref{chp:Hardware and its Habits}
> and~\ref{cha:Partitioning and Synchronization Design}.
> Having all CPUs write concurrently to the same variable
> --
> 1.9.1
>
prev parent reply other threads:[~2016-04-26 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 1:22 [PATCH] advsync: fix trivial typos SeongJae Park
2016-04-26 1:39 ` 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=20160426013906.GX3874@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=perfbook@vger.kernel.org \
--cc=sj38.park@gmail.com \
/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.