From: Jason Yan <yanaijie@huawei.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.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>,
<john.garry@huawei.com>, <jinpu.wang@cloud.ionos.com>
Subject: Re: [PATCH v3 6/8] scsi: libsas: use sas_phy_match_dev_addr() instead of open coded
Date: Tue, 27 Sep 2022 10:35:25 +0800 [thread overview]
Message-ID: <6f7983bf-cc68-0477-257c-debdcf664165@huawei.com> (raw)
In-Reply-To: <585db20d-8530-d605-ebf2-e8d669e693a8@opensource.wdc.com>
On 2022/9/27 10:30, Damien Le Moal wrote:
> On 9/27/22 11:29, Jason Yan wrote:
>> The sas address comparation of domain device and expander phy is open
>> coded. Now we can replace it with sas_phy_match_dev_addr().
>>
>> Signed-off-by: Jason Yan <yanaijie@huawei.com>
>> ---
>> drivers/scsi/libsas/sas_expander.c | 18 ++++++------------
>> 1 file changed, 6 insertions(+), 12 deletions(-)
>>
>> diff --git a/drivers/scsi/libsas/sas_expander.c b/drivers/scsi/libsas/sas_expander.c
>> index df5a64ad902f..b2b5103c3e76 100644
>> --- a/drivers/scsi/libsas/sas_expander.c
>> +++ b/drivers/scsi/libsas/sas_expander.c
>> @@ -738,9 +738,7 @@ static void sas_ex_get_linkrate(struct domain_device *parent,
>> phy->phy_state == PHY_NOT_PRESENT)
>> continue;
>>
>> - if (SAS_ADDR(phy->attached_sas_addr) ==
>> - SAS_ADDR(child->sas_addr)) {
>> -
>> + if (sas_phy_match_dev_addr(child, phy)) {
>> child->min_linkrate = min(parent->min_linkrate,
>> phy->linkrate);
>> child->max_linkrate = max(parent->max_linkrate,
>> @@ -1012,8 +1010,7 @@ static int sas_ex_discover_dev(struct domain_device *dev, int phy_id)
>> sas_add_parent_port(dev, phy_id);
>> return 0;
>> }
>> - if (dev->parent && (SAS_ADDR(ex_phy->attached_sas_addr) ==
>> - SAS_ADDR(dev->parent->sas_addr))) {
>> + if (dev->parent && sas_phy_match_dev_addr(dev->parent, ex_phy)) {
>> sas_add_parent_port(dev, phy_id);
>> if (ex_phy->routing_attr == TABLE_ROUTING)
>> sas_configure_phy(dev, phy_id, dev->port->sas_addr, 1);
>> @@ -1312,7 +1309,7 @@ static int sas_check_parent_topology(struct domain_device *child)
>> parent_phy->phy_state == PHY_NOT_PRESENT)
>> continue;
>>
>> - if (SAS_ADDR(parent_phy->attached_sas_addr) != SAS_ADDR(child->sas_addr))
>> + if (sas_phy_match_dev_addr(child, parent_phy))
>
> This changes the test. This should be:
>
> if (!sas_phy_match_dev_addr(child, parent_phy))
>
> No ?
Oh yes, my mistake. Thank you so much to point that out. Will fix.
Thanks,
Jason
>
>> continue;
>>
>> child_phy = &child_ex->ex_phy[parent_phy->attached_phy_id];
>> @@ -1522,8 +1519,7 @@ static int sas_configure_parent(struct domain_device *parent,
>> struct ex_phy *phy = &ex_parent->ex_phy[i];
>>
>> if ((phy->routing_attr == TABLE_ROUTING) &&
>> - (SAS_ADDR(phy->attached_sas_addr) ==
>> - SAS_ADDR(child->sas_addr))) {
>> + sas_phy_match_dev_addr(child, phy)) {
>> res = sas_configure_phy(parent, i, sas_addr, include);
>> if (res)
>> return res;
>> @@ -1858,8 +1854,7 @@ static void sas_unregister_devs_sas_addr(struct domain_device *parent,
>> if (last) {
>> list_for_each_entry_safe(child, n,
>> &ex_dev->children, siblings) {
>> - if (SAS_ADDR(child->sas_addr) ==
>> - SAS_ADDR(phy->attached_sas_addr)) {
>> + if (sas_phy_match_dev_addr(child, phy)) {
>> set_bit(SAS_DEV_GONE, &child->state);
>> if (dev_is_expander(child->dev_type))
>> sas_unregister_ex_tree(parent->port, child);
>> @@ -1941,8 +1936,7 @@ static int sas_discover_new(struct domain_device *dev, int phy_id)
>> if (res)
>> return res;
>> list_for_each_entry(child, &dev->ex_dev.children, siblings) {
>> - if (SAS_ADDR(child->sas_addr) ==
>> - SAS_ADDR(ex_phy->attached_sas_addr)) {
>> + if (sas_phy_match_dev_addr(child, ex_phy)) {
>> if (dev_is_expander(child->dev_type))
>> res = sas_discover_bfs_by_root(child);
>> break;
>
next prev parent reply other threads:[~2022-09-27 2:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 2:29 [PATCH v3 0/8] scsi: libsas: sas address comparation refactor Jason Yan
2022-09-27 2:29 ` [PATCH v3 1/8] scsi: libsas: introduce sas address comparation helpers Jason Yan
2022-09-27 2:23 ` Damien Le Moal
2022-09-27 2:44 ` Jason Yan
2022-09-27 2:29 ` [PATCH v3 2/8] scsi: libsas: introduce sas_find_attached_phy() helper Jason Yan
2022-09-27 2:24 ` Damien Le Moal
2022-09-27 2:29 ` [PATCH v3 3/8] scsi: pm8001: use sas_find_attached_phy() instead of open coded Jason Yan
2022-09-27 2:25 ` Damien Le Moal
2022-09-27 2:29 ` [PATCH v3 4/8] scsi: mvsas: " Jason Yan
2022-09-27 2:27 ` Damien Le Moal
2022-09-27 2:29 ` [PATCH v3 5/8] scsi: hisi_sas: use sas_find_attathed_phy() " Jason Yan
2022-09-27 2:28 ` Damien Le Moal
2022-09-27 2:29 ` [PATCH v3 6/8] scsi: libsas: use sas_phy_match_dev_addr() " Jason Yan
2022-09-27 2:30 ` Damien Le Moal
2022-09-27 2:35 ` Jason Yan [this message]
2022-09-27 2:29 ` [PATCH v3 7/8] scsi: libsas: use sas_phy_addr_match() " Jason Yan
2022-09-27 2:31 ` Damien Le Moal
2022-09-27 2:29 ` [PATCH v3 8/8] scsi: libsas: use sas_phy_match_port_addr() " Jason Yan
2022-09-27 2:32 ` Damien Le Moal
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=6f7983bf-cc68-0477-257c-debdcf664165@huawei.com \
--to=yanaijie@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=john.garry@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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®