mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Jason Yan <yanaijie@huawei.com>, <martin.petersen@oracle.com>,
	<jejb@linux.ibm.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<hare@suse.com>, <hch@lst.de>, <bvanassche@acm.org>,
	<jinpu.wang@cloud.ionos.com>, <damien.lemoal@opensource.wdc.com>,
	Jack Wang <jinpu.wang@ionos.com>
Subject: Re: [PATCH v4 2/8] scsi: libsas: introduce sas_find_attached_phy() helper
Date: Tue, 27 Sep 2022 09:46:19 +0100	[thread overview]
Message-ID: <19189c2c-91ee-f389-314f-a5133a5d3ef2@huawei.com> (raw)
In-Reply-To: <20220927032605.78103-3-yanaijie@huawei.com>

On 27/09/2022 04:25, Jason Yan wrote:
> LLDDs are implementing their own attached phy finding code repeatedly.
> Factor it out to libsas.
> 
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
> Reviewed-by: Jack Wang <jinpu.wang@ionos.com>
> Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

Apart from nit, below:
Reviewed-by: John Garry <john.garry@huawei.com>

> ---
>   drivers/scsi/libsas/sas_expander.c | 16 ++++++++++++++++
>   include/scsi/libsas.h              |  2 ++
>   2 files changed, 18 insertions(+)
> 
> diff --git a/drivers/scsi/libsas/sas_expander.c b/drivers/scsi/libsas/sas_expander.c
> index fa2209080cc2..df5a64ad902f 100644
> --- a/drivers/scsi/libsas/sas_expander.c
> +++ b/drivers/scsi/libsas/sas_expander.c
> @@ -2107,6 +2107,22 @@ int sas_ex_revalidate_domain(struct domain_device *port_dev)
>   	return res;
>   }
>   
> +int sas_find_attached_phy(struct expander_device *ex_dev,
> +			  struct domain_device *dev)

Maybe sas_find_attached_phy_id() is a better name

> +{
> +	struct ex_phy *phy;
> +	int phy_id;
> +
> +	for (phy_id = 0; phy_id < ex_dev->num_phys; phy_id++) {
> +		phy = &ex_dev->ex_phy[phy_id];
> +		if (sas_phy_match_dev_addr(dev, phy))
> +			return phy_id;
> +	}
> +
> +	return -ENODEV;
> +}
> +EXPORT_SYMBOL_GPL(sas_find_attached_phy);
> +
>   void sas_smp_handler(struct bsg_job *job, struct Scsi_Host *shost,
>   		struct sas_rphy *rphy)
>   {
> diff --git a/include/scsi/libsas.h b/include/scsi/libsas.h
> index 2dbead74a2af..75faf2308eae 100644
> --- a/include/scsi/libsas.h
> +++ b/include/scsi/libsas.h
> @@ -750,6 +750,8 @@ int sas_clear_task_set(struct domain_device *dev, u8 *lun);
>   int sas_lu_reset(struct domain_device *dev, u8 *lun);
>   int sas_query_task(struct sas_task *task, u16 tag);
>   int sas_abort_task(struct sas_task *task, u16 tag);
> +int sas_find_attached_phy(struct expander_device *ex_dev,
> +			  struct domain_device *dev);
>   
>   void sas_notify_port_event(struct asd_sas_phy *phy, enum port_event event,
>   			   gfp_t gfp_flags);


  reply	other threads:[~2022-09-27  8:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27  3:25 [PATCH v4 0/8] scsi: libsas: sas address comparison refactor Jason Yan
2022-09-27  3:25 ` [PATCH v4 1/8] scsi: libsas: introduce sas address comparison helpers Jason Yan
2022-09-27  8:38   ` John Garry
2022-09-27  3:25 ` [PATCH v4 2/8] scsi: libsas: introduce sas_find_attached_phy() helper Jason Yan
2022-09-27  8:46   ` John Garry [this message]
2022-09-27  3:26 ` [PATCH v4 3/8] scsi: pm8001: use sas_find_attached_phy() instead of open coded Jason Yan
2022-09-27  8:34   ` John Garry
2022-09-27 11:25     ` Jason Yan
2022-09-27  3:26 ` [PATCH v4 4/8] scsi: mvsas: " Jason Yan
2022-09-27  3:26 ` [PATCH v4 5/8] scsi: hisi_sas: use sas_find_attathed_phy() " Jason Yan
2022-09-27  3:26 ` [PATCH v4 6/8] scsi: libsas: use sas_phy_match_dev_addr() " Jason Yan
2022-09-27  4:25   ` Damien Le Moal
2022-09-27  3:26 ` [PATCH v4 7/8] scsi: libsas: use sas_phy_addr_match() " Jason Yan
2022-09-27  3:26 ` [PATCH v4 8/8] scsi: libsas: use sas_phy_match_port_addr() " Jason Yan

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=19189c2c-91ee-f389-314f-a5133a5d3ef2@huawei.com \
    --to=john.garry@huawei.com \
    --cc=bvanassche@acm.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=hare@suse.com \
    --cc=hch@lst.de \
    --cc=jejb@linux.ibm.com \
    --cc=jinpu.wang@cloud.ionos.com \
    --cc=jinpu.wang@ionos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=yanaijie@huawei.com \
    /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

all inboxes | Powered by JetHome®