[PATCH] local_t update documentation

[Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>]

local_t update documentation

Quoting Grant Grundler <grundler@parisc-linux.org>
> o Wording in local_ops.txt: "on the  
>   "... it will then appear to be written out of order wrt
>    other memory writes on the owner CPU."
> 
>   I'd like to suggest "by the owner CPU".
> 

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
CC: Grant Grundler <grundler@parisc-linux.org>
---
 Documentation/local_ops.txt |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-2.6-lttng/Documentation/local_ops.txt
===================================================================
--- linux-2.6-lttng.orig/Documentation/local_ops.txt	2007-08-28 07:45:39.000000000 -0400
+++ linux-2.6-lttng/Documentation/local_ops.txt	2007-08-28 07:45:47.000000000 -0400
@@ -27,7 +27,7 @@ CPU which owns the data. Therefore, care
 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

-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/