From: Jeff Garzik <jgarzik@pobox.com>
To: Brian King <brking@us.ibm.com>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 4/6] libata: Add ata_host_flags
Date: Sun, 11 Jun 2006 23:26:43 -0400 [thread overview]
Message-ID: <448CDEF3.1000703@pobox.com> (raw)
In-Reply-To: <200606071625.k57GPrit014721@d01av01.pok.ibm.com>
Brian King wrote:
> Since SATA devices attached to SAS HBAs will not have
> a host_set, add a helper function to retrieve the host_set
> flags which can check for the existence of a host_set.
>
> Signed-off-by: Brian King <brking@us.ibm.com>
> ---
>
> libata-dev-bjking1/drivers/scsi/libata-core.c | 7 +++----
> libata-dev-bjking1/include/linux/libata.h | 7 +++++++
> 2 files changed, 10 insertions(+), 4 deletions(-)
>
> diff -puN drivers/scsi/libata-core.c~libata_sas_no_simplex drivers/scsi/libata-core.c
> --- libata-dev/drivers/scsi/libata-core.c~libata_sas_no_simplex 2006-06-06 08:55:43.000000000 -0500
> +++ libata-dev-bjking1/drivers/scsi/libata-core.c 2006-06-06 08:55:43.000000000 -0500
> @@ -2161,7 +2161,7 @@ int ata_set_mode(struct ata_port *ap, st
> /* Record simplex status. If we selected DMA then the other
> * host channels are not permitted to do so.
> */
> - if (used_dma && (ap->host_set->flags & ATA_HOST_SIMPLEX))
> + if (used_dma && (ata_host_flags(ap) & ATA_HOST_SIMPLEX))
I'm not sure I like this one. Will have to think a bit more on this --
there might be a need for ipr to carry some cross-port libata state.
Jeff
next prev parent reply other threads:[~2006-06-12 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 16:25 [PATCH 4/6] libata: Add ata_host_flags Brian King
2006-06-12 3:26 ` Jeff Garzik [this message]
2006-06-12 18:33 ` Brian King
2006-06-26 18:56 ` Brian King
2006-06-26 20:54 ` Alan Cox
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=448CDEF3.1000703@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=brking@us.ibm.com \
--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).