From: Jeff Garzik <jeff@garzik.org>
To: IDE/ATA development list <linux-ide@vger.kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: libata-dev.git clean up and branch status
Date: Fri, 06 Jul 2007 20:21:10 -0400 [thread overview]
Message-ID: <468EDC76.9050708@garzik.org> (raw)
libata-dev.git was left a bit grotty when I went on vacation. That has
now been fixed. The current branches are:
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
master Always vanilla Linus tree
ALL Always the "exported for testing" meta-branch
(currently == upstream + sil680-mmio + mv-ahci)
upstream queued for 2.6.23
Parent: master
mv-ahci Marvell 6121/6141 AHCI clone SATA support
Parent: upstream
Status: Works, once NCQ & PCI MSI are disabled.
Turn these off, then can go up.
mv-ahci-pata Marvell 6121/6141 AHCI clone PATA support
Parent: mv-ahci
Status: Need to update for proper use of PATA
controller commands (provides direct access to
PATA device shadow registers)
mv-eh sata_mv (50xx/60xx) conversion to new EH
Parent: upstream
Status: Required for hotplug, NCQ, etc. Working, but
currently NCQ disks fail (even if NCQ not used)
new-eh pdc_adma, sata_qstor, sata_sx4 conversion to new EH
Parent: upstream
Status: All conversions complete...
and completely untested.
sii-lbt sata_sil Large [DMA] Block Transfer support
Parent: upstream
Status: Useful, but reported to fail in some cases
sil680-mmio pata_sil680 MMIO support
Parent: upstream
Status: dissolved into some argument about MMIO flushing
next reply other threads:[~2007-07-07 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-07 0:21 Jeff Garzik [this message]
2007-07-07 20:25 ` libata-dev.git clean up and branch status Alan Cox
2008-07-25 11:35 ` Alan Cox
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=468EDC76.9050708@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--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 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.