Discussions of the Parallel Programming book
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Emilio G. Cota" <cota@braap.org>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH] advsync: s/an write/a write/
Date: Thu, 9 Apr 2015 16:02:56 -0700	[thread overview]
Message-ID: <20150409230256.GR6464@linux.vnet.ibm.com> (raw)
In-Reply-To: <1428610555-27168-1-git-send-email-cota@braap.org>

On Thu, Apr 09, 2015 at 04:15:55PM -0400, Emilio G. Cota wrote:
> Signed-off-by: Emilio G. Cota <cota@braap.org>

Queued, thank you!

							Thanx, Paul

> ---
>  advsync/memorybarriers.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/advsync/memorybarriers.tex b/advsync/memorybarriers.tex
> index e8666db..2d16542 100644
> --- a/advsync/memorybarriers.tex
> +++ b/advsync/memorybarriers.tex
> @@ -1777,7 +1777,7 @@ always be paired.  A lack of appropriate pairing is almost certainly an error.
> 
>  A write barrier should always be paired with a data dependency barrier or read
>  barrier, though a general barrier would also be viable.  Similarly a read
> -barrier or a data dependency barrier should always be paired with at least an
> +barrier or a data dependency barrier should always be paired with at least a
>  write barrier, though, again, a general barrier is viable:
> 
>  \vspace{5pt}
> -- 
> 1.9.1
> 
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2015-04-09 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 20:15 [PATCH] advsync: s/an write/a write/ Emilio G. Cota
2015-04-09 23:02 ` 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=20150409230256.GR6464@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=cota@braap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox