From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
amsden_linux@earthlink.net
Subject: Re: [PATCH 1/2 #upstream] libata: udpate ata_dev_try_classify() arguments
Date: Fri, 31 Aug 2007 05:18:29 -0400 [thread overview]
Message-ID: <46D7DCE5.8090700@garzik.org> (raw)
In-Reply-To: <20070808053739.GS13674@htj.dyndns.org>
Tejun Heo wrote:
> Make ata_dev_try_classify() take a pointer to ata_device instead of
> ata_port/port_number combination for consistency and add @present
> argument. @present indicates whether the device seems present during
> reset. It's the result of TF access during softreset and link
> onlineness during hardreset. @present will be used to improve
> diagnostic failure handling.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> drivers/ata/libata-core.c | 31 +++++++++++++++++--------------
> drivers/ata/pata_scc.c | 6 ++++--
> drivers/ata/sata_mv.c | 2 +-
> include/linux/libata.h | 3 ++-
> 4 files changed, 24 insertions(+), 18 deletions(-)
ACK patches 1-2
request rediff+resend
next prev parent reply other threads:[~2007-08-31 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 5:37 [PATCH 1/2 #upstream] libata: udpate ata_dev_try_classify() arguments Tejun Heo
2007-08-08 5:40 ` [PATCH 2/2 #upstream] libata: assume ATA_DEV_ATA on diagnostic failure Tejun Heo
2007-08-08 8:33 ` Alan Cox
2007-08-31 9:18 ` Jeff Garzik [this message]
2007-09-02 14:23 ` [PATCH 1/2 #upstream,REGENERATED] libata: udpate ata_dev_try_classify() arguments Tejun Heo
2007-09-02 14:24 ` [PATCH 2/2 #upstream,REGENERATED] libata: assume ATA_DEV_ATA on diagnostic failure Tejun Heo
2007-09-20 21:32 ` [PATCH 1/2 #upstream,REGENERATED] libata: udpate ata_dev_try_classify() arguments 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=46D7DCE5.8090700@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=amsden_linux@earthlink.net \
--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).