>From 41b970ba205df9069ce9921211e6214a4c138354 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Sun, 26 Mar 2017 00:16:07 +0900
Subject: [RFC PATCH 05/12] advsync: Add footnote mentioning LOCK/UNLOCK wording
The text of the footnote should be regarded as a stub.
Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
advsync/memorybarriers.tex | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/advsync/memorybarriers.tex b/advsync/memorybarriers.tex
index ae6ca9f..60d32b0 100644
--- a/advsync/memorybarriers.tex
+++ b/advsync/memorybarriers.tex
@@ -1556,7 +1556,11 @@ because they are embedded into locking primitives:
\begin{enumerate}
\item ACQUIRE operations and
-\item RELEASE operations.
+\item RELEASE operations.\footnote{
+ Note that there were times when ACQUIRE/RELEASE operations
+ were called as ``LOCK/UNLOCK'' operations in the Linux
+ kernel community. ``ACQUIRE/RELEASE'' is preferred in
+ discussing lockless techniques.}
\end{enumerate}
\paragraph{ACQUIRE Operations}
--
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
