Commit d6f459bc authored by Andrew Morton's avatar Andrew Morton Committed by Linus Torvalds

[PATCH] spin_lock_irqrestore() typo fixes

From: Vinay K Nallamothu <vinay-rc@naturesoft.net>

s/spin_lock_irqrestore/spin_unlock_irqrestore/
parent 464319bf
...@@ -463,7 +463,7 @@ ...@@ -463,7 +463,7 @@
<function>spin_lock_irqsave()</function> <function>spin_lock_irqsave()</function>
(<filename>include/linux/spinlock.h</filename>) is a variant (<filename>include/linux/spinlock.h</filename>) is a variant
which saves whether interrupts were on or off in a flags word, which saves whether interrupts were on or off in a flags word,
which is passed to <function>spin_lock_irqrestore()</function>. This which is passed to <function>spin_unlock_irqrestore()</function>. This
means that the same code can be used inside an hard irq handler (where means that the same code can be used inside an hard irq handler (where
interrupts are already off) and in softirqs (where the irq interrupts are already off) and in softirqs (where the irq
disabling is required). disabling is required).
......
...@@ -218,7 +218,7 @@ ...@@ -218,7 +218,7 @@
* interrupt time. * interrupt time.
* - digi_write_bulk_callback() and digi_read_bulk_callback() are * - digi_write_bulk_callback() and digi_read_bulk_callback() are
* called directly from interrupts. Hence spin_lock_irqsave() * called directly from interrupts. Hence spin_lock_irqsave()
* and spin_lock_irqrestore() are used in the rest of the code * and spin_unlock_irqrestore() are used in the rest of the code
* for any locks they acquire. * for any locks they acquire.
* - digi_write_bulk_callback() gets the port lock before waking up * - digi_write_bulk_callback() gets the port lock before waking up
* processes sleeping on the port write_wait. It also schedules * processes sleeping on the port write_wait. It also schedules
...@@ -571,7 +571,7 @@ static struct usb_serial_device_type digi_acceleport_4_device = { ...@@ -571,7 +571,7 @@ static struct usb_serial_device_type digi_acceleport_4_device = {
* *
* Do spin_unlock_irqrestore and interruptible_sleep_on_timeout * Do spin_unlock_irqrestore and interruptible_sleep_on_timeout
* so that wake ups are not lost if they occur between the unlock * so that wake ups are not lost if they occur between the unlock
* and the sleep. In other words, spin_lock_irqrestore and * and the sleep. In other words, spin_unlock_irqrestore and
* interruptible_sleep_on_timeout are "atomic" with respect to * interruptible_sleep_on_timeout are "atomic" with respect to
* wake ups. This is used to implement condition variables. * wake ups. This is used to implement condition variables.
*/ */
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment