All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH 3/3] memorder: Fix trivial typo
Date: Sat, 18 Nov 2017 12:10:27 -0800	[thread overview]
Message-ID: <20171118201027.GM3624@linux.vnet.ibm.com> (raw)
In-Reply-To: <c2a30f43-d49c-807f-ffe0-e51bf1b3d639@gmail.com>

On Sun, Nov 19, 2017 at 12:07:02AM +0900, Akira Yokosawa wrote:
> >From a2d0cd80fb99a15bd5265f12863ac8f0183f9a9b Mon Sep 17 00:00:00 2001
> From: Akira Yokosawa <akiyks@gmail.com>
> Date: Sat, 18 Nov 2017 23:39:26 +0900
> Subject: [PATCH 3/3] memorder: Fix trivial typo
> 
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>

I applied all three, and especially like the script taking up some
of the manual handling of quick quizzes with figures!

One thing I left out, please see below.

							Thanx, Paul

> ---
>  memorder/memorder.tex | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/memorder/memorder.tex b/memorder/memorder.tex
> index 68dc09b..d11df62 100644
> --- a/memorder/memorder.tex
> +++ b/memorder/memorder.tex
> @@ -10,7 +10,7 @@ Causality and sequencing are deeply intuitive, and hackers often
>  tend to have a much stronger grasp of these concepts than does
>  the general population.
>  These intuitions can be extremely powerful tools when writing, analyzing,
> -and debugging both sequential code and parallel code that makes
> +and debugging both sequential code and parallel code that make
>  use of standard mutual-exclusion mechanisms, such as locking and
>  RCU.
>  Unfortunately, these intuitions break down completely in face of

If it was "intuitions" that made use of "standard mutual-exclusion
mechanisms", this fix would be correct.  Plural "intuitions" would
require plural "make".  (And no, I have no idea why English adds "s"
to nouns to denote plural, but removes "s" from verbs to denote plural.
Probably because it is English...)

But it is "code" that made use of "standard mutual-exclusion mechanisms".
I am treating "code" like "water", that is, "lines of code" would be
plural (like "molecules of water"), but "code" is singular (like "water").

I also treat "data" as singular, that is, as a collective noun.  This
is controversial, and people who like "data" to be plural probably also
like "code" to be plural when referring to lines of code.

https://en.wikipedia.org/wiki/Data_(word)

And it appears that most people are now willing to put up with "data"
as a collective noun when applied to computers.  Others are probably
still protesting that "data" is the plural form of "datum" in Latin.

But, yes, English!  :-/

							Thanx, Paul

> @@ -38,7 +38,7 @@ follows up with more detail on what representative hardware platforms
>  actually do to unwary parallel programmers.
>  Finally, Section~\ref{sec:memorder:Where is Memory Ordering Needed?}
>  provides some rules of thumb for what situations require parallel
> -programmers to take special action to preserver memory ordering.
> +programmers to take special action to preserve memory ordering.
> 
>  \section{Ordering: Why and How?}
>  \label{sec:memorder:Ordering: Why and How?}
> -- 
> 2.7.4
> 
> 


  reply	other threads:[~2017-11-18 20:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-18 15:03 [PATCH 0/3] Update qqzreorder.pl Akira Yokosawa
2017-11-18 15:04 ` [PATCH 1/3] Update qqzreorder.pl to take care of listing at the end of QQA Akira Yokosawa
2017-11-18 15:06 ` [PATCH 2/3] Partial revert of 'Fix layout hiccups in answers to quick quizzes' Akira Yokosawa
2017-11-18 15:07 ` [PATCH 3/3] memorder: Fix trivial typo Akira Yokosawa
2017-11-18 20:10   ` Paul E. McKenney [this message]
2017-11-18 22:43     ` 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=20171118201027.GM3624@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 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.