From: Jason Yan <yanaijie@huawei.com>
To: John Garry <john.garry@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 3/8] scsi: pm8001: use sas_find_attached_phy() instead of open coded
Date: Tue, 27 Sep 2022 19:25:39 +0800 [thread overview]
Message-ID: <cc8a0c09-03a2-c7e2-5f1a-c9b740315b70@huawei.com> (raw)
In-Reply-To: <9e9f8384-0662-73ef-ab17-8420c94762fb@huawei.com>
On 2022/9/27 16:34, John Garry wrote:
> On 27/09/2022 04:26, Jason Yan wrote:
>> +++ b/drivers/scsi/pm8001/pm8001_sas.c
>> @@ -645,22 +645,16 @@ static int pm8001_dev_found_notify(struct
>> domain_device *dev)
>> pm8001_device->dcompletion = &completion;
>> if (parent_dev && dev_is_expander(parent_dev->dev_type)) {
>> int phy_id;
>> - struct ex_phy *phy;
>> - for (phy_id = 0; phy_id < parent_dev->ex_dev.num_phys;
>> - phy_id++) {
>> - phy = &parent_dev->ex_dev.ex_phy[phy_id];
>> - if (SAS_ADDR(phy->attached_sas_addr)
>> - == SAS_ADDR(dev->sas_addr)) {
>> - pm8001_device->attached_phy = phy_id;
>> - break;
>> - }
>> - }
>> - if (phy_id == parent_dev->ex_dev.num_phys) {
>> +
>> + phy_id = sas_find_attached_phy(&parent_dev->ex_dev, dev);
>> + if (phy_id == -ENODEV) {
>> pm8001_dbg(pm8001_ha, FAIL,
>> "Error: no attached dev:%016llx at ex:%016llx.\n",
>> SAS_ADDR(dev->sas_addr),
>> SAS_ADDR(parent_dev->sas_addr));
>> res = -1;
>
> I think that you can just pass the linux error code (-ENODEV) back here.
>
> And for hisi_sas we change to -EINVAL for this code. I don't think it's
> required, so I think that we can pass -ENODEV back there also. Using
> -EINVAL seems to come from when the code was originally added in
> abda97c2fe874 and from a quick glance libsas does not seem to have
> special processing for -EINVAL.
>
Yes, libsas does not have any special processing for the return value,
so there is no difference in what value we return here. But I agree with
you that return -ENODEV is better here because we can keep it consistent
with the return value of sas_find_attached_phy().
Will update.
Thanks,
Jason
> Thanks,
> John
>
>> + } else {
>> + pm8001_device->attached_phy = phy_id;
>> }
>> } else {
>> if (dev->dev_type == SAS_SATA
>
> .
next prev parent reply other threads:[~2022-09-27 11:28 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
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 [this message]
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=cc8a0c09-03a2-c7e2-5f1a-c9b740315b70@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=jinpu.wang@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®