From: Hannes Reinecke <hare@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/3] scsi_transport_sas: add is_sas_attached() function
Date: Tue, 15 Dec 2015 11:16:37 +0100 [thread overview]
Message-ID: <566FE885.4070204@suse.de> (raw)
In-Reply-To: <1449688323.2226.32.camel@HansenPartnership.com>
On 12/09/2015 08:12 PM, James Bottomley wrote:
> Adds a function designed to be callable any time (regardless of
> whether the transport attributes are configured or not) which returns
> true if the device is attached over a SAS transport. The design of
> this function is that transport specific functions can be embedded
> within a
>
> if (is_sas_attached(sdev)) {
> ...
> }
>
> which would be compiled out (and thus eliminate the symbols) if SAS is
> not configured.
>
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> ---
> drivers/scsi/scsi_transport_sas.c | 16 ++++++++++++++++
> include/scsi/scsi_transport_sas.h | 9 +++++++++
> 2 files changed, 25 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/scsi/scsi_transport_sas.c b/drivers/scsi/scsi_transport_sas.c
> index 30d26e3..b17f763 100644
> --- a/drivers/scsi/scsi_transport_sas.c
> +++ b/drivers/scsi/scsi_transport_sas.c
> @@ -341,6 +341,22 @@ static int do_sas_phy_delete(struct device *dev, void *data)
> }
>
> /**
> + * is_sas_attached - check if device is SAS attached
> + * @sdev: scsi device to check
> + *
> + * returns true if the device is SAS attached
> + */
> +int is_sas_attached(struct scsi_device *sdev)
> +{
> + struct Scsi_Host *shost = sdev->host;
> +
> + return shost->transportt->host_attrs.ac.class ==
> + &sas_host_class.class;
> +}
> +EXPORT_SYMBOL(is_sas_attached);
> +
> +
> +/**
> * sas_remove_children - tear down a devices SAS data structures
> * @dev: device belonging to the sas object
> *
> diff --git a/include/scsi/scsi_transport_sas.h b/include/scsi/scsi_transport_sas.h
> index 0bd71e2..a8fdd10 100644
> --- a/include/scsi/scsi_transport_sas.h
> +++ b/include/scsi/scsi_transport_sas.h
> @@ -10,6 +10,15 @@ struct scsi_transport_template;
> struct sas_rphy;
> struct request;
>
> +#if !IS_ENABLED(CONFIG_SCSI_SAS_ATTRS)
> +static inline int is_sas_attached(struct scsi_device *sdev)
> +{
> + return 0;
> +}
> +#else
> +extern int is_sas_attached(struct scsi_device *sdev);
> +#endif
> +
> static inline int sas_protocol_ata(enum sas_protocol proto)
> {
> return ((proto & SAS_PROTOCOL_SATA) ||
>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-15 10:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 19:10 [PATCH 0/3] Fix the problem of SATA devices within SAS enclosures James Bottomley
2015-12-09 19:12 ` [PATCH 1/3] scsi_transport_sas: add is_sas_attached() function James Bottomley
2015-12-15 10:16 ` Hannes Reinecke [this message]
2015-12-09 19:13 ` [PATCH 2/3] scsi_transport_sas: add function to get SAS endpoint address James Bottomley
2015-12-15 10:17 ` Hannes Reinecke
2015-12-09 19:14 ` [PATCH 3/3] ses: fix discovery of SATA devices in SAS enclosures James Bottomley
2015-12-09 20:38 ` kbuild test robot
2015-12-09 20:52 ` James Bottomley
2015-12-09 20:56 ` [PATCH v2 " James Bottomley
2015-12-15 10:17 ` Hannes Reinecke
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=566FE885.4070204@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--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 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.