From: Jeff Garzik <jgarzik@pobox.com>
To: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [SATA] libata-dev-2.6 queue updated
Date: Mon, 15 Nov 2004 01:43:46 -0500 [thread overview]
Message-ID: <20041115064346.GA14449@havoc.gtf.org> (raw)
BK users:
bk pull bk://gkernel.bkbits.net/libata-dev-2.6
Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.10-rc2-libata1-dev1.patch.bz2
This will update the following files:
drivers/scsi/Kconfig | 8
drivers/scsi/Makefile | 1
drivers/scsi/libata-core.c | 38 ++
drivers/scsi/libata-scsi.c | 409 +++++++++++++++++++++++++
drivers/scsi/libata.h | 2
drivers/scsi/pata_pdc2027x.c | 694 +++++++++++++++++++++++++++++++++++++++++++
drivers/scsi/sata_promise.c | 56 +++
include/linux/ata.h | 1
include/linux/libata.h | 2
include/scsi/scsi.h | 3
10 files changed, 1203 insertions(+), 11 deletions(-)
through these ChangeSets:
<albertcc:tw.ibm.com>:
o [libata pdc2027x] fix incorrect pio and mwdma masks
o [libata pdc2027x] remove quirks and ROM enable
o [libata] add driver for Promise PATA 2027x
<andyw:pobox.com>:
o [libata scsi] support 12-byte passthru CDB
o [libata scsi] passthru CDB check condition processing
o T10/04-262 ATA pass thru - patch
<erikbenada:yahoo.ca>:
o [libata sata_promise] support PATA ports on SATA controllers
Brad Campbell:
o libata basic detection and errata for PATA->SATA bridges
Jeff Garzik:
o [libata pdc2027x] update for upstream struct device conversion
o [libata sata_promise] fix merge bugs
o [libata] fix build breakage
o [libata] fix SATA->PATA bridge detect compile breakage
o [libata] fix printk warning
John W. Linville:
o libata: SMART support via ATA pass-thru
Tobias Lorenz:
o libata-scsi: get-identity ioctl support
next reply other threads:[~2004-11-15 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 6:43 Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-03 9:35 [SATA] libata-dev-2.6 queue updated Jeff Garzik
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=20041115064346.GA14449@havoc.gtf.org \
--to=jgarzik@pobox.com \
--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).