From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCHES] add ata scsi driver
Date: Mon, 26 May 2003 01:36:27 -0400 [thread overview]
Message-ID: <3ED1A7DB.1000507@pobox.com> (raw)
In-Reply-To: <3ED1A664.1020307@pobox.com>
Jeff Garzik wrote:
> So, I conclude: faster, smaller, and better future direction. IMO, of
> course :)
As a FWIW, this driver is mainly intended as a Serial ATA driver.
It just happens to do PATA by coincedence (i.e. because it makes devel
easier for me).
For example, current Intel SATA is "PATA, but without the timing junk."
I think with SATA + drivers/ide, you reach a point of diminishing
returns versus amount of time spent on mid-layer coding.
Jeff
next prev parent reply other threads:[~2003-05-26 5:23 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 4:58 [BK PATCHES] add ata scsi driver Jeff Garzik
2003-05-26 5:15 ` Linus Torvalds
2003-05-26 5:30 ` Jeff Garzik
2003-05-26 5:36 ` Jeff Garzik [this message]
2003-05-26 5:42 ` Linus Torvalds
2003-05-26 6:01 ` Jeff Garzik
2003-05-26 16:56 ` Linus Torvalds
2003-05-26 17:47 ` Jeff Garzik
2003-05-26 20:09 ` Linus Torvalds
2003-05-27 0:29 ` Alan Cox
2003-05-27 6:07 ` Jeff Garzik
2003-05-27 6:30 ` Linus Torvalds
2003-05-27 6:51 ` Linus Torvalds
2003-05-27 7:29 ` Jeff Garzik
2003-05-26 5:40 ` Linus Torvalds
2003-05-26 5:53 ` Jeff Garzik
2003-05-26 6:21 ` Jeff Garzik
2003-05-26 16:57 ` Linus Torvalds
2003-05-26 17:24 ` Jens Axboe
2003-05-26 17:54 ` Jeff Garzik
2003-05-26 17:59 ` Jeff Garzik
2003-05-26 18:11 ` Jens Axboe
2003-05-27 0:22 ` Alan Cox
2003-05-27 4:15 ` Linus Torvalds
2003-05-26 10:32 ` Bartlomiej Zolnierkiewicz
2003-05-26 11:13 ` Jeff Garzik
2003-05-26 11:37 ` Bartlomiej Zolnierkiewicz
2003-05-26 5:59 ` Benjamin Herrenschmidt
2003-05-26 6:03 ` Jeff Garzik
2003-06-02 9:46 ` Andre Hedrick
2003-06-02 13:56 ` Alan Cox
2003-05-26 18:12 James Bottomley
2003-05-26 18:18 ` Jens Axboe
2003-05-26 18:47 ` James Bottomley
2003-05-26 19:07 ` Jens Axboe
2003-05-26 19:17 ` James Bottomley
2003-05-26 19:33 ` Jens Axboe
2003-05-27 12:39 ` Jens Axboe
2003-05-27 14:26 ` James Bottomley
2003-05-27 17:16 ` Jens Axboe
2003-05-27 18:09 ` James Bottomley
2003-05-27 18:21 ` Jens Axboe
2003-05-27 18:30 ` James Bottomley
2003-05-26 20:27 ` Linus Torvalds
2003-05-26 20:36 ` James Bottomley
2003-05-26 20:45 ` Linus Torvalds
2003-05-26 20:51 ` Jens Axboe
2003-05-26 20:56 ` James Bottomley
2003-05-26 20:38 ` Jens Axboe
2003-05-26 20:49 ` Linus Torvalds
2003-05-26 20:57 ` Jens Axboe
2003-05-26 21:34 ` Linus Torvalds
2003-05-26 23:58 ` Nick Piggin
2003-05-27 0:09 ` Linus Torvalds
2003-05-27 0:49 ` Nick Piggin
2003-05-27 0:16 ` Alan Cox
2003-05-27 6:54 ` Jens Axboe
2003-05-27 14:20 ` James Bottomley
2003-05-27 14:36 ` Linus Torvalds
2003-05-27 14:59 ` James Bottomley
2003-05-27 15:21 ` Jeff Garzik
2003-05-27 15:38 ` James Bottomley
2003-05-27 15:50 ` Jeff Garzik
2003-05-27 16:00 ` James Bottomley
2003-05-27 16:16 ` Jeff Garzik
2003-05-28 9:35 ` Christoph Hellwig
2003-05-28 10:50 ` Lincoln Dale
2003-05-27 19:43 ` 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=3ED1A7DB.1000507@pobox.com \
--to=jgarzik@pobox.com \
--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;
as well as URLs for NNTP newsgroup(s).