From: Jens Axboe <axboe@suse.de>
To: Sean <seanlkml@rogers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] "blk: request botched" error on floppy write
Date: Mon, 21 Jul 2003 14:33:31 +0200 [thread overview]
Message-ID: <20030721123331.GE10781@suse.de> (raw)
In-Reply-To: <794001c34e24$d8f83440$7f0a0a0a@lappy7>
On Sat, Jul 19 2003, Sean wrote:
> The floppy drive appears to be working for some people with the
> 2.6 kernel as is. However, there have also been reports of some
> problems (see http://bugme.osdl.org/show_bug.cgi?id=654 )
>
> The attached patch against 2.6.0-test1 fixes the problem on all the
> machines i've tested.
So floppy has a problem with clustered requests? Your patch doesn't fix
that bug, it masks it.
Question is, if we should just accept that and move on. I mean, who
really cares?
--
Jens Axboe
next prev parent reply other threads:[~2003-07-21 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 18:37 [PATCH] "blk: request botched" error on floppy write Sean
2003-07-21 12:33 ` Jens Axboe [this message]
2003-07-21 12:39 ` Mr. James W. Laferriere
2003-07-21 13:36 ` Jens Axboe
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=20030721123331.GE10781@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=seanlkml@rogers.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