From: Jeff Garzik <jgarzik@pobox.com>
To: LKML <linux-kernel@vger.kernel.org>, linux-scsi@vger.kernel.org
Subject: libata update posted
Date: Tue, 12 Aug 2003 23:40:42 -0400 [thread overview]
Message-ID: <3F39B33A.2050709@pobox.com> (raw)
Well, I was hoping to complete another low-level driver (Silicon Image)
out there, but I would rather get bug fixes out first :)
libata driver architecture version 0.70 (helper library)
Intel ICH5 SATA driver version 0.93
Patch for 2.4.21:
ftp://ftp.??.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.4/2.4.21-libata5.patch.bz2
Patch for 2.6.0-test3:
ftp://ftp.??.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/2.6.0-test3-bk1-libata1.patch.bz2
Stressed on both 2.4 and 2.6, SMP and UP, lba2[48] and lba48.
Changes:
* lba48 fix
* SMP fixes
* locking sanitization
* locking documentation ("make pdfdocs")
* more infrastructure for command queueing and async taskfiles
Notes:
* Parallel ATA limited to UDMA/33 (SATA is full speed)
* ATAPI not ready for prime time
Still no data-corrupting bugs, knock on wood.
next reply other threads:[~2003-08-13 3:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 3:40 Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-13 3:23 libata update posted Jeff Garzik
2003-09-13 20:56 ` J.A. Magallon
2003-09-13 21:28 ` Jeff Garzik
2003-09-14 9:12 ` Andries Brouwer
2003-09-14 17:26 ` Jeff Garzik
2003-09-14 19:38 ` Andries Brouwer
2003-09-14 20:09 ` Jeff Garzik
2003-09-14 21:09 ` Andries Brouwer
2003-09-14 21:36 ` Jeff Garzik
2003-09-14 21:38 ` James Bottomley
2003-09-14 22:18 ` Andries Brouwer
2003-09-16 19:34 ` Pavel Machek
2003-09-13 21:13 ` J.A. Magallon
2003-09-13 21:38 ` Jeff Garzik
2003-09-14 22:27 ` Hugo Mills
2003-09-14 22:31 ` Jeff Garzik
2003-10-05 23:15 Jeff Garzik
2003-10-05 23:41 ` Bartlomiej Zolnierkiewicz
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=3F39B33A.2050709@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.