path: root/Documentation/kernel-hacking
diff options
authorJonathan Corbet <>2018-07-26 16:17:55 -0600
committerJonathan Corbet <>2018-07-26 16:17:55 -0600
commitc8cce10a62aaaca33bbdbe7356bde20a47790290 (patch)
tree9e62006d75b0e5027d570d8f4e0cfe1a510ce5d3 /Documentation/kernel-hacking
parent1fee4f77523a3e5a44fa33c9aa76de8c6c42a632 (diff)
docs: Fix the reference labels in Locking.rst
Two jump tags were misspelled, leading to non-working cross-reference links. Reported-by: Federico Vaga <> Signed-off-by: Jonathan Corbet <>
Diffstat (limited to 'Documentation/kernel-hacking')
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/kernel-hacking/locking.rst b/Documentation/kernel-hacking/locking.rst
index f937c0fd11aa..9cc036ff57b9 100644
--- a/Documentation/kernel-hacking/locking.rst
+++ b/Documentation/kernel-hacking/locking.rst
@@ -177,7 +177,7 @@ perfect world).
Note that you can also use :c:func:`spin_lock_irq()` or
:c:func:`spin_lock_irqsave()` here, which stop hardware interrupts
-as well: see `Hard IRQ Context <#hardirq-context>`__.
+as well: see `Hard IRQ Context <#hard-irq-context>`__.
This works perfectly for UP as well: the spin lock vanishes, and this
macro simply becomes :c:func:`local_bh_disable()`
@@ -228,7 +228,7 @@ The Same Softirq
The same softirq can run on the other CPUs: you can use a per-CPU array
-(see `Per-CPU Data <#per-cpu>`__) for better performance. If you're
+(see `Per-CPU Data <#per-cpu-data>`__) for better performance. If you're
going so far as to use a softirq, you probably care about scalable
performance enough to justify the extra complexity.