[PATCH 19/25] Docs: kernel-hacking: CPU id on [0,NR_CPUS)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Clarify and correct the return value of get_cpu()
and introduce better wording.

Signed-off-by: Michael Witten <mfwitten@xxxxxxxxx>
---
 Documentation/DocBook/kernel-hacking.tmpl |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/DocBook/kernel-hacking.tmpl b/Documentation/DocBook/kernel-hacking.tmpl
index 92632f3..511f2f3 100644
--- a/Documentation/DocBook/kernel-hacking.tmpl
+++ b/Documentation/DocBook/kernel-hacking.tmpl
@@ -815,9 +815,9 @@
    
    <para>
     <function>get_cpu()</function> disables preemption (so you won't
-    suddenly get moved to another CPU) and returns the current
-    processor number, between 0 and <symbol>NR_CPUS</symbol>.  Note
-    that the CPU numbers are not necessarily continuous.  You return
+    suddenly get moved to another CPU) and returns as the current
+    CPU id a number on the half-open interval [0,<symbol>NR_CPUS</symbol>);
+    subsequently returned CPU ids are not necessarily contiguous.  You return
     it again with <function>put_cpu()</function> when you are done.
    </para>
    <para>
-- 
1.7.0.94.gf7311

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux