>From a2d0cd80fb99a15bd5265f12863ac8f0183f9a9b Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Sat, 18 Nov 2017 23:39:26 +0900
Subject: [PATCH 3/3] memorder: Fix trivial typo
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
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
@@ -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
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
