All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: jeff@garzik.org, linux-ide@vger.kernel.org
Subject: [PATCHSET #upstream] libata: improve ATAPI data transfer handling, take #4
Date: Wed,  2 Jan 2008 20:12:46 +0900	[thread overview]
Message-ID: <11992723701811-git-send-email-htejun@gmail.com> (raw)


Hello,

This is the fourth take of improve-ATAPI-data-transfer patchset.
Changes from the last take [L] are

* Patches other than 8, 13, 14 and 15 have been committed to #upstream
  and thus dropped from this patchset.

* Due to merge order, pata_pcmcia is now out-of-sync with data_xfer
  prototype update.  A patch was added to convert pata_pcmcia.

* Patch 13, 14 and 15 are updated to apply on top of the current
  #upstream.

This patchset is agaisnt the current #upstream (32a03e13).

Thanks.

--
tejun

[L] http://thread.gmane.org/gmane.linux.ide/25938

             reply	other threads:[~2008-01-02 11:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 11:12 Tejun Heo [this message]
2008-01-02 11:12 ` [PATCH 1/4] sata_qstor: convert to new data_xfer prototype Tejun Heo
2008-01-02 13:51   ` [PATCH 1/4] pata_pcmcia: " Tejun Heo
2008-01-16 10:24   ` [PATCH 1/4] sata_qstor: " Jeff Garzik
2008-01-02 11:12 ` [PATCH 2/4] libata: update ATAPI overflow draining Tejun Heo
2008-02-01 20:34   ` Jeff Garzik
2008-02-07  0:14   ` Jeff Garzik
2008-01-02 11:12 ` [PATCH 3/4] libata: implement ATAPI drain buffer Tejun Heo
2008-01-10 17:30   ` [RFC 1/2] block: implement drain buffers James Bottomley
2008-01-10 17:42     ` [RFC 2/2] libata: " James Bottomley
2008-01-14 16:01     ` [RFC 1/2] block: " James Bottomley
2008-02-07  0:14   ` [PATCH 3/4] libata: implement ATAPI drain buffer Jeff Garzik
2008-01-02 11:12 ` [PATCH 4/4] libata: implement ATAPI per-command-type DMA horkages Tejun Heo
2008-01-02 13:34   ` Alan Cox
2008-01-02 13:49     ` Tejun Heo

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=11992723701811-git-send-email-htejun@gmail.com \
    --to=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@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.