public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [PATCH] local_t update documentation
@ 2007-08-28 11:51 Mathieu Desnoyers
  0 siblings, 0 replies; only message in thread
From: Mathieu Desnoyers @ 2007-08-28 11:51 UTC (permalink / raw)
  To: akpm, linux-kernel

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2007-08-28 11:51 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-28 11:51 [PATCH] local_t update documentation Mathieu Desnoyers

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox