From: Vinay K Nallamothu <vinay-rc@naturesoft.net>
To: Trivial Patch Monkey <trivial@rustcorp.com.au>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 2.6.0-test4][TRIVIAL][USB] digi_acceleport.c: typo fix spin_lock_irqrestore
Date: 23 Aug 2003 19:59:20 +0530 [thread overview]
Message-ID: <1061648960.2787.54.camel@lima.royalchallenge.com> (raw)
--- linux-2.6.0-test4/drivers/usb/serial/digi_acceleport.c 2003-08-23 13:14:37.000000000 +0530
+++ linux-2.6.0-test4-nvk/drivers/usb/serial/digi_acceleport.c 2003-08-23 19:35:29.000000000 +0530
@@ -218,7 +218,7 @@
* interrupt time.
* - digi_write_bulk_callback() and digi_read_bulk_callback() are
* 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.
* - digi_write_bulk_callback() gets the port lock before waking up
* processes sleeping on the port write_wait. It also schedules
@@ -571,7 +571,7 @@
*
* Do spin_unlock_irqrestore and interruptible_sleep_on_timeout
* 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
* wake ups. This is used to implement condition variables.
*/
next reply other threads:[~2003-08-23 14:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 14:29 Vinay K Nallamothu [this message]
2003-08-27 21:57 ` [PATCH 2.6.0-test4][TRIVIAL][USB] digi_acceleport.c: typo fix spin_lock_irqrestore Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1061648960.2787.54.camel@lima.royalchallenge.com \
--to=vinay-rc@naturesoft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox