* [PATCH] advsync: s/an write/a write/
@ 2015-04-09 20:15 Emilio G. Cota
2015-04-09 23:02 ` Paul E. McKenney
0 siblings, 1 reply; 2+ messages in thread
From: Emilio G. Cota @ 2015-04-09 20:15 UTC (permalink / raw)
To: perfbook
Signed-off-by: Emilio G. Cota <cota@braap.org>
---
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
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] advsync: s/an write/a write/
2015-04-09 20:15 [PATCH] advsync: s/an write/a write/ Emilio G. Cota
@ 2015-04-09 23:02 ` Paul E. McKenney
0 siblings, 0 replies; 2+ messages in thread
From: Paul E. McKenney @ 2015-04-09 23:02 UTC (permalink / raw)
To: Emilio G. Cota; +Cc: perfbook
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
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-04-09 23:03 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-04-09 20:15 [PATCH] advsync: s/an write/a write/ Emilio G. Cota
2015-04-09 23:02 ` Paul E. McKenney
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.