From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] libata: replace ap->cbl tests with ATA_FLAG_SATA tests
Date: Thu, 24 May 2007 23:05:56 -0400 [thread overview]
Message-ID: <46565294.50905@garzik.org> (raw)
In-Reply-To: <4651C9EB.2040707@gmail.com>
Tejun Heo wrote:
> ap->cbl == ATA_CBL_SATA indicates SATA cable while ap->flags &
> ATA_FLAG_SATA indicates SATA host port. Till now they always gave the
> same result but SATA/PATA bridge handling will change that. Switch to
> ATA_FLAG_SATA test if we're testing for host port type.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
> ---
> libata-core.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
applied
prev parent reply other threads:[~2007-05-25 3:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 16:33 [PATCH] libata: replace ap->cbl tests with ATA_FLAG_SATA tests Tejun Heo
2007-05-21 16:58 ` Alan Cox
2007-05-25 3:05 ` Jeff Garzik [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=46565294.50905@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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).