From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Tejun Heo <htejun@gmail.com>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp,
Jens.Axboe@oracle.com
Subject: Re: [PATCHSET #upstream] block/libata: update and use block layer padding and draining
Date: Wed, 06 Feb 2008 17:31:29 -0600 [thread overview]
Message-ID: <1202340689.3112.140.camel@localhost.localdomain> (raw)
In-Reply-To: <12021979851743-git-send-email-htejun@gmail.com>
On Tue, 2008-02-05 at 16:53 +0900, Tejun Heo wrote:
> This patchset updates block layer padding and draining support and
> make libata use it. It's based on James Bottomley's initial work and,
> of the five, the last two patches are from James with some
> modifications.
>
> Please read the following thread for more info.
>
> http://thread.gmane.org/gmane.linux.scsi/37185
>
> This patchset is on top of
>
> upstream (a6af42fc9a12165136d82206ad52f18c5955ce87)
> + kill-n_iter-and-fix-fsl patch [1]
This certainly fixes the SATAPI panic on aic94xx (finally got the
machine with it plugged into the expanders to boot).
James
next prev parent reply other threads:[~2008-02-06 23:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 7:53 [PATCHSET #upstream] block/libata: update and use block layer padding and draining Tejun Heo
2008-02-05 7:53 ` [PATCH 1/5] block: update bio according to DMA alignment padding Tejun Heo
2008-02-05 7:53 ` [PATCH 2/5] block: add request->raw_data_len Tejun Heo
2008-02-05 7:53 ` [PATCH 3/5] block: implement request_queue->dma_drain_needed Tejun Heo
2008-02-05 7:53 ` [PATCH 4/5] libata: eliminate the home grown dma padding in favour of that provided by the block layer Tejun Heo
2008-02-05 7:53 ` [PATCH 5/5] libata: implement drain buffers Tejun Heo
2008-02-06 23:31 ` James Bottomley [this message]
2008-02-07 0:09 ` [PATCHSET #upstream] block/libata: update and use block layer padding and draining Jeff Garzik
2008-02-08 20:56 ` Jeff Garzik
2008-02-08 21:04 ` Jens Axboe
2008-02-08 21:48 ` Jeff Garzik
2008-02-09 0:22 ` 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=1202340689.3112.140.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Jens.Axboe@oracle.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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).