From: Albert Lee <albertcc@tw.ibm.com>
To: Jeff Garzik <jgarzik@pobox.com>, Tejun Heo <htejun@gmail.com>
Cc: alan@lxorguk.ukuu.org.uk, axboe@suse.de, forrest.zhao@intel.com,
efalk@google.com, linux-ide@vger.kernel.org
Subject: Re: [PATCHSET 04/11] merge irq-pio
Date: Tue, 16 May 2006 18:00:24 +0800 [thread overview]
Message-ID: <4469A2B8.9020901@tw.ibm.com> (raw)
In-Reply-To: <44665980.1020308@pobox.com>
Jeff Garzik wrote:
> Tejun Heo wrote:
>
>> Howdy,
>>
>> This is part of patchset series described in [T].
>>
>> This patchset contains merge of irq-pio branch. This patchset is
>> composed of two patches - the first one is the merge and the second
>> one contains follow-up fixes.
>>
>> THIS PATCHSET IS FOR REVIEW ONLY. Please pull from the git tree
>> described in [T] for proper credit attribution and merge history.
>
>
> I of course ACK this patchset.
>
> I'm highly interested in "it works" feedback from Albert and Alan <hint
> hint>... :)
>
Sorry for the late reply.
I've downloaded the upstream branch. The irq-pio merge looks fine.
Also run minimal test with pata_pdc2027x/sata_via; the reset and normal read/write looks good.
Thanks for the great new features to play with. :)
Will do more test later.
--
albert
prev parent reply other threads:[~2006-05-16 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 13:33 [PATCHSET 04/11] merge irq-pio Tejun Heo
2006-05-11 13:33 ` [PATCH] libata: fix irq-pio merge Tejun Heo
2006-05-11 13:33 ` [PATCH] libata: merge irq-pio Tejun Heo
2006-05-23 10:05 ` Albert Lee
2006-05-23 10:12 ` [PATCH 1/1] libata: minor fix for irq-pio merge Albert Lee
2006-05-23 20:09 ` [PATCH] libata: merge irq-pio Jeff Garzik
2006-05-26 8:14 ` Albert Lee
2006-05-27 0:53 ` Tejun Heo
2006-05-13 22:11 ` [PATCHSET 04/11] " Jeff Garzik
2006-05-16 10:00 ` Albert Lee [this message]
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=4469A2B8.9020901@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=axboe@suse.de \
--cc=efalk@google.com \
--cc=forrest.zhao@intel.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--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.