[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20180605194326.23596-1-j.neuschaefer@gmx.net>
Date: Tue, 5 Jun 2018 21:43:23 +0200
From: Jonathan Neuschäfer <j.neuschaefer@....net>
To: linux-doc@...r.kernel.org
Cc: Jonathan Neuschäfer <j.neuschaefer@....net>,
Jonathan Corbet <corbet@....net>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH] docs: atomic_ops: atomic_set is a write (not read) operation
Describe it as such.
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@....net>
---
Documentation/core-api/atomic_ops.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/core-api/atomic_ops.rst b/Documentation/core-api/atomic_ops.rst
index 2e7165f86f55..724583453e1f 100644
--- a/Documentation/core-api/atomic_ops.rst
+++ b/Documentation/core-api/atomic_ops.rst
@@ -29,7 +29,7 @@ updated by one CPU, local_t is probably more appropriate. Please see
local_t.
The first operations to implement for atomic_t's are the initializers and
-plain reads. ::
+plain writes. ::
#define ATOMIC_INIT(i) { (i) }
#define atomic_set(v, i) ((v)->counter = (i))
--
2.17.1
Powered by blists - more mailing lists