linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: IDE/ATA development list <linux-ide@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Tejun Heo <htejun@gmail.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Alan <alan@lxorguk.ukuu.org.uk>,
	Jens Axboe <jens.axboe@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
	Jason Gaston <jason.d.gaston@intel.com>
Subject: Re: What's left in libata-dev.git?
Date: Thu, 25 Oct 2007 05:59:21 -0400	[thread overview]
Message-ID: <472068F9.3070700@garzik.org> (raw)
In-Reply-To: <472067FD.3060400@garzik.org>

Jeff Garzik wrote:
> Active libata branches:
>   ALL            Superset branch for -mm testing
>   alpm            Link power management (2.6.24-rc hopefully)
>   an            Async notify (2.6.24-rc hopefully)
>   for-testing        Interesting-but-not-ready stuff
>   master        Vanilla linux-2.6.git clone
>   mv-ahci-pata        Marvell 6141 PATA support (incomplete)
>   mv-ncq        sata_mv NCQ support (incomplete)
>   new-eh        sata_qstore, sata_sx4 new-EH conversions
>             (TEST ME! they have been in -mm for a while)
>   pmask            proto_mask introduction
>   sii-lbt        sata_sil large block transfer enablement
>   upstream        pending for 2.6.24-rc
>   upstream-linus    just pushed upstream for 2.6.24-rc


FWIW, current contents of ALL meta-branch:

	upstream
	an
	alpm
	for-testing
	new-eh

i.e. that is what akpm will get on his next pull for -mm.


  reply	other threads:[~2007-10-25  9:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25  9:55 What's left in libata-dev.git? Jeff Garzik
2007-10-25  9:59 ` Jeff Garzik [this message]
2007-10-25 10:05 ` Tejun Heo
2007-10-25 10:11   ` 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=472068F9.3070700@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bzolnier@gmail.com \
    --cc=htejun@gmail.com \
    --cc=jason.d.gaston@intel.com \
    --cc=jens.axboe@oracle.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-ide@vger.kernel.org \
    --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 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).