summaryrefslogtreecommitdiffstats
path: root/Documentation/local_ops.txt
diff options
context:
space:
mode:
authorMathieu Desnoyers <mathieu.desnoyers@polymtl.ca>2007-10-17 08:29:29 +0200
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-10-17 17:42:56 +0200
commit0e1ccb9619e8e9ae86dfc5a4645ccf3bf5a2eb3f (patch)
treee5366b5c950d870f6c07bf627061ff0c08bc623b /Documentation/local_ops.txt
parentatomic_ops.txt: mention local_t (diff)
downloadlinux-0e1ccb9619e8e9ae86dfc5a4645ccf3bf5a2eb3f.tar.xz
linux-0e1ccb9619e8e9ae86dfc5a4645ccf3bf5a2eb3f.zip
local_t: update documentation
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> Cc: Grant Grundler <grundler@parisc-linux.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to '')
-rw-r--r--Documentation/local_ops.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/local_ops.txt b/Documentation/local_ops.txt
index a134a563db32..4269a1105b37 100644
--- a/Documentation/local_ops.txt
+++ b/Documentation/local_ops.txt
@@ -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