path: root/Documentation/DocBook/kernel-locking.tmpl
diff options
authorMatthew Wilcox <>2008-04-18 22:21:05 -0400
committerMatthew Wilcox <>2008-04-18 22:22:54 -0400
commit6188e10d38b8d7244ee7776d5f1f88c837b4b93f (patch)
tree6675e02c47fb684a613e10513816b5dcc5de28a9 /Documentation/DocBook/kernel-locking.tmpl
parentd7b1acd3b524b39f418e463e836b48ac041954d6 (diff)
Convert asm/semaphore.h users to linux/semaphore.h
Signed-off-by: Matthew Wilcox <>
Diffstat (limited to 'Documentation/DocBook/kernel-locking.tmpl')
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/DocBook/kernel-locking.tmpl b/Documentation/DocBook/kernel-locking.tmpl
index 2e9d6b41f034..435413ca40dc 100644
--- a/Documentation/DocBook/kernel-locking.tmpl
+++ b/Documentation/DocBook/kernel-locking.tmpl
@@ -241,7 +241,7 @@
The third type is a semaphore
- (<filename class="headerfile">include/asm/semaphore.h</filename>): it
+ (<filename class="headerfile">include/linux/semaphore.h</filename>): it
can have more than one holder at any time (the number decided at
initialization time), although it is most commonly used as a
single-holder lock (a mutex). If you can't get a semaphore, your
@@ -290,7 +290,7 @@
If you have a data structure which is only ever accessed from
user context, then you can use a simple semaphore
- (<filename>linux/asm/semaphore.h</filename>) to protect it. This
+ (<filename>linux/linux/semaphore.h</filename>) to protect it. This
is the most trivial case: you initialize the semaphore to the number
of resources available (usually 1), and call
<function>down_interruptible()</function> to grab the semaphore, and
@@ -1656,7 +1656,7 @@ the amount of locking which needs to be done.
#include &lt;linux/slab.h&gt;
#include &lt;linux/string.h&gt;
+#include &lt;linux/rcupdate.h&gt;
- #include &lt;asm/semaphore.h&gt;
+ #include &lt;linux/semaphore.h&gt;
#include &lt;asm/errno.h&gt;
struct object