From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IDE: strange WAIT_READY dependency on APM
Date: Fri, 10 Dec 2004 15:20:05 +0000 [thread overview]
Message-ID: <1102692003.3201.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20041209034438.GF22324@stusta.de>
On Iau, 2004-12-09 at 03:44, Adrian Bunk wrote:
> The time for the !APM case was already increased from 30msec in 2.4 .
> Isn't there a timeout that is suitable for all cases?
The five seconds should be just fine for all cases. The smaller value
with no
power manglement should help speed up recovery however. It probably
doesn't belong CONFIG_APM now ACPI and friends are involved either.
next prev parent reply other threads:[~2004-12-10 16:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 3:44 IDE: strange WAIT_READY dependency on APM Adrian Bunk
2004-12-09 10:53 ` Pavel Machek
2004-12-10 15:20 ` Alan Cox [this message]
2004-12-11 17:30 ` [2.6 patch] IDE: remove " Adrian Bunk
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=1102692003.3201.5.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bunk@stusta.de \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox