From: Russell King <rmk+lkml@arm.linux.org.uk>
To: janitor@sternwelten.at
Cc: akpm@digeo.com, linux-kernel@vger.kernel.org, nacc@us.ibm.com
Subject: Re: [patch 4/4] mmc: replace schedule_timeout() with msleep_interruptible()
Date: Wed, 29 Sep 2004 14:44:11 +0100 [thread overview]
Message-ID: <20040929144411.C16537@flint.arm.linux.org.uk> (raw)
In-Reply-To: <E1CAaWc-0002s3-Fd@sputnik>; from janitor@sternwelten.at on Thu, Sep 23, 2004 at 10:49:10PM +0200
On Thu, Sep 23, 2004 at 10:49:10PM +0200, janitor@sternwelten.at wrote:
> Description: Use msleep_interruptible() instead of schedule_timeout()
> to guarantee the task delays as expected.
Applied, thanks.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
prev parent reply other threads:[~2004-09-29 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 20:49 [patch 4/4] mmc: replace schedule_timeout() with msleep_interruptible() janitor
2004-09-29 13:44 ` Russell King [this message]
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=20040929144411.C16537@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@digeo.com \
--cc=janitor@sternwelten.at \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@us.ibm.com \
/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