From: David Woodhouse <dwmw2@infradead.org>
To: janitor@sternwelten.at
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, nacc@us.ibm.com
Subject: Re: [patch 07/10] mtd/amd_flash: replace schedule_timeout() with msleep()
Date: Sat, 20 Nov 2004 12:59:35 +0000 [thread overview]
Message-ID: <1100955575.8600.29.camel@localhost.localdomain> (raw)
In-Reply-To: <E1CVL5L-0001V3-BQ@sputnik>
On Sat, 2004-11-20 at 03:34 +0100, janitor@sternwelten.at wrote:
>
>
> Any comments would be appreciated.
>
> Description: Use msleep() instead of schedule_timeout()
> to guarantee the task delays as expected.
Applied; thanks. Likewise the ones for cfi_cmdset_0002.c and
cfi_cmdset_0020.c. The one for cfi_cmdset_0001.c doesn't apply any more
-- that just uses the cfi_udelay() helper function. So I fixed that too.
All in bk://linux-mtd.bkbits.net/mtd-2.6 and hence should be -mm$NEXT.
--
dwmw2
prev parent reply other threads:[~2004-11-20 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-20 2:34 [patch 07/10] mtd/amd_flash: replace schedule_timeout() with msleep() janitor
2004-11-20 12:59 ` David Woodhouse [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=1100955575.8600.29.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=akpm@osdl.org \
--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