Documentation: preempt-locking: Use better example
authorAndrew Murray <andrew.murray@arm.com>
Mon, 8 Oct 2018 13:15:15 +0000 (14:15 +0100)
committerJonathan Corbet <corbet@lwn.net>
Fri, 12 Oct 2018 17:35:47 +0000 (11:35 -0600)
commit44280690ced5dacd3004d4966ef9b15f940f34e0
tree8d4a42b829b48e74be0301ebf9fcf1c761a9a066
parent0c6c987f3706fedff42eee5384c7ede8a910c4ed
Documentation: preempt-locking: Use better example

The existing wording implies that the use of spin_unlock whilst irqs are
disabled might trigger a reschedule. However the preemptible() test in
preempt_schedule will prevent a reschedule if irqs are disabled.

Lets improve the clarity of this wording to change the example from
spin_unlock to cond_resched() and cond_resched_lock() as these are
functions that will trigger a reschedule if the preempt count is 0 without
testing that irqs are disabled.

Also remove the 'Last Updated' line as this is not up to date and better
tracked via GIT.

Signed-off-by: Andrew Murray <andrew.murray@arm.com>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Documentation/preempt-locking.txt