From: "David S. Miller" <davem@davemloft.net>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org,
kernel-janitors@lists.osdl.org
Subject: Re: [PATCH 19/39] net/dev: replace schedule_timeout() with msleep()
Date: Tue, 8 Feb 2005 16:52:09 -0800 [thread overview]
Message-ID: <20050208165209.0481fb9d.davem@davemloft.net> (raw)
In-Reply-To: <20050120235352.GH2600@us.ibm.com>
On Thu, 20 Jan 2005 15:53:52 -0800
Nishanth Aravamudan <nacc@us.ibm.com> wrote:
> Description: Use msleep() instead of schedule_timeout() to guarantee the task
> delays as expected. The current code uses TASK_INTERRUPTIBLE, but does not
> respond to signals, so msleep() should be ok.
>
> Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
Applied, thanks Nishanth.
prev parent reply other threads:[~2005-02-09 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 23:53 [KJ] [PATCH 19/39] net/dev: replace schedule_timeout() with msleep() Nishanth Aravamudan
2005-02-09 0:52 ` David S. Miller [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=20050208165209.0481fb9d.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kernel-janitors@lists.osdl.org \
--cc=linux-net@vger.kernel.org \
--cc=nacc@us.ibm.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).