From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matthew Zahorik <matt@albany.net>
Cc: Andrew Morton <akpm@digeo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: sd driver NOT_READY behavior / was Re: How does the disk buffer cache work?
Date: 01 Jan 2003 21:32:24 +0000 [thread overview]
Message-ID: <1041456744.21748.12.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <Pine.BSF.4.43.0301011400060.370-100000@ender.tmmz.net>
On Wed, 2003-01-01 at 19:19, Matthew Zahorik wrote:
> What is the correct behavior that I should implement?
>
> a. if !removable && not ready then error
> b. if not ready then increase count until threshold then error
> c if not ready then error
> d. none of the above
I would go for a time limit (you don't want to keep spamming the same
command but to poll politely really IMHO)
prev parent reply other threads:[~2003-01-01 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 0:33 Matthew Zahorik
2002-12-31 1:24 ` Andrew Morton
2002-12-31 2:58 ` Matthew Zahorik
2002-12-31 4:14 ` Andrew Morton
2003-01-01 19:19 ` sd driver NOT_READY behavior / was " Matthew Zahorik
2003-01-01 21:32 ` Alan Cox [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=1041456744.21748.12.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@albany.net \
/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
all inboxes | Powered by JetHome®