Skip to contentSkip to conversation

advsync: s/an write/a write/

PATCH Applied Emilio G. Cota 2 participants 2 messages Apr 9, 2015

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 advsync: s/an write/a write/

---
 advsync/memorybarriers.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
advsync/memorybarriers.tex +1 -1
index e8666db..2d16542 100644
@@ -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}
Signature · 1 line
1.9.1
#1 lore raw
Quoted 1 line · Emilio G. Cota

Queued, thank you!

Thanx, Paul

Quoted 25 lines
---
 advsync/memorybarriers.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
advsync/memorybarriers.tex +1 -1
index e8666db..2d16542 100644
@@ -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}
Signature · 6 lines
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html