From: Nishanth Aravamudan <nacc@us.ibm.com>
To: kernel-janitors@vger.kernel.org
Subject: [KJ] [PATCH] 14/34: cdrom/mcdx: replace interruptible_sleep_on()
Date: Tue, 25 Jan 2005 23:18:30 +0000 [thread overview]
Message-ID: <20050125231830.GD12649@us.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
Hi,
Please consider applying.
Description: Use wait_event() instead of interruptible_sleep_on(). First,
signals are not dealt with, so *interruptible* seems unnecessary. Second, the
xtrace lines will now only be displayed once, instead of once per loop
iteration. Patch is compile-tested.
Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
--- 2.6.11-rc2-kj-v/drivers/cdrom/mcdx.c 2005-01-24 09:34:04.000000000 -0800
+++ 2.6.11-rc2-kj/drivers/cdrom/mcdx.c 2005-01-24 14:09:11.000000000 -0800
@@ -68,6 +68,7 @@ static const char *mcdx_c_version
#include <linux/mm.h>
#include <linux/slab.h>
#include <linux/init.h>
+#include <linux/wait.h>
#include <asm/io.h>
#include <asm/current.h>
#include <asm/uaccess.h>
@@ -910,11 +911,9 @@ static int mcdx_talk(struct s_drive_stuf
if ((discard = (buffer == NULL)))
buffer = &c;
- while (stuffp->lock) {
- xtrace(SLEEP, "*** talk: lockq\n");
- interruptible_sleep_on(&stuffp->lockq);
- xtrace(SLEEP, "talk: awoken\n");
- }
+ xtrace(SLEEP, "*** talk: lockq\n");
+ wait_event(stuffp->lockq, !stuffp->lock);
+ xtrace(SLEEP, "talk: awoken\n");
stuffp->lock = 1;
@@ -1341,9 +1340,7 @@ static int mcdx_xfer(struct s_drive_stuf
return -1;
}
- while (stuffp->lock) {
- interruptible_sleep_on(&stuffp->lockq);
- }
+ wait_event(stuffp->lockq, !stuffp->lock);
if (stuffp->valid && (sector >= stuffp->pending)
&& (sector < stuffp->low_border)) {
[-- Attachment #2: Type: text/plain, Size: 167 bytes --]
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors
reply other threads:[~2005-01-25 23:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050125231830.GD12649@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=kernel-janitors@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.