From: Andrew Morton <akpm@osdl.org>
To: domen@coderock.org
Cc: linux-kernel@vger.kernel.org, domen@coderock.org,
nacc@us.ibm.com, Mikael Starvik <mikael.starvik@axis.com>
Subject: Re: [patch 10/14] serial/crisv10: replace schedule_timeout() with msleep()
Date: Sun, 6 Mar 2005 19:35:48 -0800 [thread overview]
Message-ID: <20050306193548.1d0d6e44.akpm@osdl.org> (raw)
In-Reply-To: <20050306223647.3C19F1EDA4@trashy.coderock.org>
domen@coderock.org wrote:
>
> Use msleep() instead of schedule_timeout() to guarantee the task
> delays as expected. The current code uses TASK_INTERRUPTIBLE, but does not care
> about signals, so I believe msleep() should be ok.
>
> Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
> Signed-off-by: Domen Puncer <domen@coderock.org>
> ---
>
>
> kj-domen/drivers/serial/crisv10.c | 6 ++----
> 1 files changed, 2 insertions(+), 4 deletions(-)
>
> diff -puN drivers/serial/crisv10.c~msleep-drivers_serial_crisv10 drivers/serial/crisv10.c
> --- kj/drivers/serial/crisv10.c~msleep-drivers_serial_crisv10 2005-03-05 16:10:52.000000000 +0100
> +++ kj-domen/drivers/serial/crisv10.c 2005-03-05 16:10:52.000000000 +0100
> @@ -3757,10 +3757,8 @@ rs_write(struct tty_struct * tty, int fr
> e100_enable_rx_irq(info);
> #endif
>
> - if (info->rs485.delay_rts_before_send > 0) {
> - set_current_state(TASK_INTERRUPTIBLE);
> - schedule_timeout((info->rs485.delay_rts_before_send * HZ)/1000);
> - }
> + if (info->rs485.delay_rts_before_send > 0)
> + msleep(info->rs485.delay_rts_before_send);
Behavioural change: we'll no longer break out of the sleep if a signal is
pending. Which probably means you fixed a bug ;)
Please work it with Mikael.
next prev parent reply other threads:[~2005-03-07 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-06 22:36 [patch 10/14] serial/crisv10: replace schedule_timeout() with msleep() domen
2005-03-07 3:35 ` Andrew Morton [this message]
[not found] <BFECAF9E178F144FAEF2BF4CE739C668026F8BAA@exmail1.se.axis.com>
2005-03-07 8:13 ` Mikael Starvik
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=20050306193548.1d0d6e44.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=domen@coderock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.com \
--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