From: Robert Love <rml@tech9.net>
To: Andre Hedrick <andre@linuxdiskcert.org>
Cc: Jens Axboe <axboe@suse.de>, Anton Altaparmakov <aia21@cam.ac.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] 2.5.3-pre1 ata-253p1-2
Date: 17 Jan 2002 18:13:35 -0500 [thread overview]
Message-ID: <1011309216.2668.205.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.10.10201171455360.344-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10201171455360.344-100000@master.linux-ide.org>
On Thu, 2002-01-17 at 17:59, Andre Hedrick wrote:
> This kernel is totally ACB-IO or Taskfile Driven, the Config.in Option is
> to allow user-space access for diagnostics, forensics and OEM feature
> sets.
Oh, OK -- 2.5.3-pre1 doesn't have Configure.help entries ;)
But I think Anton sent them, so hopefully we will see them.
I guess the configure option just enables the ioctl, then, eh? Gotcha.
> You have to give Jens the credit for gluing it togather, because there was
> no way I would have figured out the suttle issues of BIO. There are
> serveral additions need to fix all the archs so hope to have something
> today.
Well, good work to both of you. It is an excellent driver. Please
submit it for pre2.
FYI, I am having no problems with the above and preempt-kernel, which
I've heard reported otherwise. If it works with preemption and SMP ...
Robert Love
next prev parent reply other threads:[~2002-01-17 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 13:46 [patch] 2.5.3-pre1 ide updates Jens Axboe
2002-01-17 14:29 ` Anton Altaparmakov
2002-01-17 14:28 ` Jens Axboe
2002-01-17 14:29 ` Jens Axboe
2002-01-17 14:34 ` [PATCH] 2.5.3-pre1 ata-253p1-2 Jens Axboe
2002-01-17 22:16 ` Robert Love
2002-01-17 22:59 ` Andre Hedrick
2002-01-17 23:13 ` Robert Love [this message]
2002-01-18 1:00 ` Anton Altaparmakov
2002-01-18 7:58 ` 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=1011309216.2668.205.camel@phantasy \
--to=rml@tech9.net \
--cc=aia21@cam.ac.uk \
--cc=andre@linuxdiskcert.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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