diff --git a/Documentation/kernel-hacking/locking.rst b/Documentation/kernel-hacking/locking.rst index a8518ac0d31d93f24f9a6d723d39f1a75a17140c..9850c1e526073bc6e41dcd50ab784b5875f35bf5 100644 --- a/Documentation/kernel-hacking/locking.rst +++ b/Documentation/kernel-hacking/locking.rst @@ -263,7 +263,7 @@ by a hardware interrupt on another CPU. This is where interrupts on that cpu, then grab the lock. :c:func:`spin_unlock_irq()` does the reverse. -The irq handler does not to use :c:func:`spin_lock_irq()`, because +The irq handler does not need to use :c:func:`spin_lock_irq()`, because the softirq cannot run while the irq handler is running: it can use :c:func:`spin_lock()`, which is slightly faster. The only exception would be if a different hardware irq handler uses the same lock: