The description of local_bh_{disable,enable} is now a little
clearer.
Signed-off-by: Michael Witten <mfwitten@xxxxxxxxx>
---
Documentation/DocBook/kernel-hacking.tmpl | 17 +++++++++++++----
1 files changed, 13 insertions(+), 4 deletions(-)
diff --git a/Documentation/DocBook/kernel-hacking.tmpl b/Documentation/DocBook/kernel-hacking.tmpl
index 8f8f350..d8fac2b 100644
--- a/Documentation/DocBook/kernel-hacking.tmpl
+++ b/Documentation/DocBook/kernel-hacking.tmpl
@@ -793,10 +793,19 @@
<para>
These routines disable or enable soft[ware] interrupts on the local CPU.
- They are reentrant; if soft interrupts were
- disabled before, they will still be disabled after this pair
- of functions has been called. They prevent softirqs and tasklets
- from running on the current CPU.
+ As with <function>local_irq_{save,restore}()</function>, if soft interrupts
+ are already disabled when <function>local_bh_disable()</function> is
+ called, then soft interrupts remain disabled when the corresponding
+ <function>local_bh_enable()</function> is called.
</para>
+
+ <para>
+ These routines prevent softirqs and tasklets from running on the
+ local CPU.
+ </para>
+
+ <para>
+ These routines are reentrant.
+ </para>
</sect1>
--
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
