|author||Mathieu Desnoyers <email@example.com>||2007-10-16 23:29:29 -0700|
|committer||Linus Torvalds <firstname.lastname@example.org>||2007-10-17 08:42:56 -0700|
local_t: update documentation
Signed-off-by: Mathieu Desnoyers <email@example.com> Cc: Grant Grundler <firstname.lastname@example.org> Signed-off-by: Andrew Morton <email@example.com> Signed-off-by: Linus Torvalds <firstname.lastname@example.org>
Diffstat (limited to 'Documentation/local_ops.txt')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/local_ops.txt b/Documentation/local_ops.txt
index a134a563db32..4269a1105b37 100644
@@ -27,7 +27,7 @@ CPU which owns the data. Therefore, care must taken to make sure that only one
CPU writes to the local_t data. This is done by using per cpu data and making
sure that we modify it from within a preemption safe context. It is however
permitted to read local_t data from any CPU : it will then appear to be written
-out of order wrt other memory writes on the owner CPU.
+out of order wrt other memory writes by the owner CPU.
* Implementation for a given architecture