public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Jordan Hargrave <jharg93@gmail.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	jbottomley@odin.com, jordan_hargrave@dell.com
Subject: Re: [PATCH] Remove check for SAS expander when querying bay/enclosure IDs.
Date: Tue, 14 Jul 2015 13:23:35 +0200	[thread overview]
Message-ID: <55A4F137.8010100@suse.de> (raw)
In-Reply-To: <1436797653-9822-1-git-send-email-jordan_hargrave@dell.com>

On 07/13/2015 04:27 PM, Jordan Hargrave wrote:
> Dell Server backplanes can report bay/enclosure IDs without an
> expander present.  This patch allows the bay/enclosure IDs to be
> propagaged to sysfs.we
> 
> Signed-off-by: Jordan Hargrave <jordan_hargrave@dell.com>
> ---
>  drivers/scsi/scsi_transport_sas.c | 10 ----------
>  1 file changed, 10 deletions(-)
> 
> diff --git a/drivers/scsi/scsi_transport_sas.c b/drivers/scsi/scsi_transport_sas.c
> index 9a05819..30d26e3 100644
> --- a/drivers/scsi/scsi_transport_sas.c
> +++ b/drivers/scsi/scsi_transport_sas.c
> @@ -1222,13 +1222,6 @@ show_sas_rphy_enclosure_identifier(struct device *dev,
>  	u64 identifier;
>  	int error;
>  
> -	/*
> -	 * Only devices behind an expander are supported, because the
> -	 * enclosure identifier is a SMP feature.
> -	 */
> -	if (scsi_is_sas_phy_local(phy))
> -		return -EINVAL;
> -
>  	error = i->f->get_enclosure_identifier(rphy, &identifier);
>  	if (error)
>  		return error;
> @@ -1248,9 +1241,6 @@ show_sas_rphy_bay_identifier(struct device *dev,
>  	struct sas_internal *i = to_sas_internal(shost->transportt);
>  	int val;
>  
> -	if (scsi_is_sas_phy_local(phy))
> -		return -EINVAL;
> -
>  	val = i->f->get_bay_identifier(rphy);
>  	if (val < 0)
>  		return val;
> 
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)

  reply	other threads:[~2015-07-14 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 14:27 [PATCH] Remove check for SAS expander when querying bay/enclosure IDs Jordan Hargrave
2015-07-14 11:23 ` Hannes Reinecke [this message]
2015-08-31 16:26   ` Jordan Hargrave

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=55A4F137.8010100@suse.de \
    --to=hare@suse.de \
    --cc=jbottomley@odin.com \
    --cc=jharg93@gmail.com \
    --cc=jordan_hargrave@dell.com \
    --cc=linux-kernel@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