From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: linux-ide@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ide-taskfile.c fixups/cleanups part #2 [4/9]
Date: Wed, 30 Jun 2004 11:10:25 -0500 [thread overview]
Message-ID: <1088611825.1921.18.camel@gaston> (raw)
In-Reply-To: <200406301725.05181.bzolnier@elka.pw.edu.pl>
On Wed, 2004-06-30 at 10:25, Bartlomiej Zolnierkiewicz wrote:
> [PATCH] ide: remove BUSY check from task_in_intr() (CONFIG_IDE_TASKFILE_IO=n)
>
> We shouldn't ever get there if drive is busy and we can't start transfer
> in this case. ide-disk.c:read_intr() also doesn't check for BUSY_STAT bit.
What if we have a shared interrupt with another device ?
Ben.
next prev parent reply other threads:[~2004-06-30 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 15:25 [PATCH] ide-taskfile.c fixups/cleanups part #2 [4/9] Bartlomiej Zolnierkiewicz
2004-06-30 16:10 ` Benjamin Herrenschmidt [this message]
2004-06-30 17:16 ` Bartlomiej Zolnierkiewicz
2004-06-30 17:12 ` Benjamin Herrenschmidt
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=1088611825.1921.18.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-ide@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).