From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCHSET] libata: implement and use ata_dev_revalidate(), take #3
Date: Sun, 05 Mar 2006 11:10:56 -0500 [thread overview]
Message-ID: <440B0D90.2080005@pobox.com> (raw)
In-Reply-To: <11415489584127-git-send-email-htejun@gmail.com>
Tejun Heo wrote:
> Hello, Jeff.
>
> This is the third take of implement-and-use-ata_dev_revalidate
> patchset. In the last take[1], out of four patches, %1, %2 and %4 got
> ACK'ed while %3 had some minor issues.
>
> Changes from the last take are...
>
> * in #3, ata_dev_same_device() tags mismatch messages with KERN_INFO
> instead of KERN_WARNING.
>
> * in #3, ata_dev_revalidate() returns -ENODEV instead of 0 if device
> isn't present
I thought this was take #4? Anyway...
applied 1-4
next prev parent reply other threads:[~2006-03-05 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 8:55 [PATCHSET] libata: implement and use ata_dev_revalidate(), take #3 Tejun Heo
2006-03-05 8:55 ` [PATCH 3/4] libata: implement ata_dev_revalidate() Tejun Heo
2006-03-05 8:55 ` [PATCH 4/4] libata: revalidate after transfer mode configuration Tejun Heo
2006-03-05 8:55 ` [PATCH 1/4] libata: re-initialize parameters before configuring Tejun Heo
2006-03-05 16:10 ` Jeff Garzik [this message]
2006-03-05 16:33 ` [PATCHSET] libata: implement and use ata_dev_revalidate(), take #3 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=440B0D90.2080005@pobox.com \
--to=jgarzik@pobox.com \
--cc=htejun@gmail.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 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).