From: John Garry <john.g.garry@oracle.com>
To: Jason Yan <yanaijie@huawei.com>,
martin.petersen@oracle.com, jejb@linux.ibm.com
Cc: linux-scsi@vger.kernel.org, hare@suse.com, hch@lst.de,
bvanassche@acm.org, jinpu.wang@cloud.ionos.com,
damien.lemoal@opensource.wdc.com
Subject: Re: [PATCH 2/6] scsi: libsas: delete wrapper function sas_discover_end_dev()
Date: Mon, 5 Dec 2022 08:57:26 +0000 [thread overview]
Message-ID: <8729c1c5-c306-1fdc-ff30-174740be97c4@oracle.com> (raw)
In-Reply-To: <20221204081643.3835966-3-yanaijie@huawei.com>
On 04/12/2022 08:16, Jason Yan wrote:
> After commit 0558f33c06bb ("scsi: libsas: direct call probe and destruct")
> this function is only a wrapper of sas_notify_lldd_dev_found(). And the
> function name does not reflect the real purpose of this function now.
Why is this? Maybe add "dev_found" to the name could help.
> Remove it and call sas_notify_lldd_dev_found() directly. The log is also
> changed accordingly.
>
> Cc: John Garry <john.g.garry@oracle.com>
> Signed-off-by: Jason Yan <yanaijie@huawei.com>
> ---
> drivers/scsi/libsas/sas_discover.c | 13 +------------
> drivers/scsi/libsas/sas_expander.c | 4 ++--
> include/scsi/libsas.h | 1 -
> 3 files changed, 3 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/scsi/libsas/sas_discover.c b/drivers/scsi/libsas/sas_discover.c
> index d5bc1314c341..efc6bf95bb67 100644
> --- a/drivers/scsi/libsas/sas_discover.c
> +++ b/drivers/scsi/libsas/sas_discover.c
> @@ -269,17 +269,6 @@ static void sas_resume_devices(struct work_struct *work)
> sas_resume_sata(port);
> }
>
> -/**
> - * sas_discover_end_dev - discover an end device (SSP, etc)
> - * @dev: pointer to domain device of interest
> - *
> - * See comment in sas_discover_sata().
> - */
> -int sas_discover_end_dev(struct domain_device *dev)
> -{
> - return sas_notify_lldd_dev_found(dev);
> -}
> -
> /* ---------- Device registration and unregistration ---------- */
>
> void sas_free_device(struct kref *kref)
> @@ -447,7 +436,7 @@ static void sas_discover_domain(struct work_struct *work)
>
> switch (dev->dev_type) {
> case SAS_END_DEVICE:
> - error = sas_discover_end_dev(dev);
> + error = sas_notify_lldd_dev_found(dev);
For me, personally, I prefer consistent API name, like
sas_discover_end_dev() and sas_discover_sata(), even if
sas_discover_end_dev() is just a wrapper.
> break;
> case SAS_EDGE_EXPANDER_DEVICE:
> case SAS_FANOUT_EXPANDER_DEVICE:
> diff --git a/drivers/scsi/libsas/sas_expander.c b/drivers/scsi/libsas/sas_expander.c
> index a04cad620e93..aa8ea3b1f2e4 100644
> --- a/drivers/scsi/libsas/sas_expander.c
> +++ b/drivers/scsi/libsas/sas_expander.c
> @@ -855,9 +855,9 @@ static struct domain_device *sas_ex_discover_end_dev(
>
> list_add_tail(&child->disco_list_node, &parent->port->disco_list);
>
> - res = sas_discover_end_dev(child);
> + res = sas_notify_lldd_dev_found(child);
> if (res) {
> - pr_notice("sas_discover_end_dev() for device %016llx at %016llx:%02d returned 0x%x\n",
> + pr_notice("notify lldd for device %016llx at %016llx:%02d returned 0x%x\n",
> SAS_ADDR(child->sas_addr),
> SAS_ADDR(parent->sas_addr), phy_id, res);
> goto out_list_del;
> diff --git a/include/scsi/libsas.h b/include/scsi/libsas.h
> index 1aee3d0ebbb2..87682390fb76 100644
> --- a/include/scsi/libsas.h
> +++ b/include/scsi/libsas.h
> @@ -736,7 +736,6 @@ void sas_init_disc(struct sas_discovery *disc, struct asd_sas_port *);
> void sas_discover_event(struct asd_sas_port *, enum discover_event ev);
>
> int sas_discover_sata(struct domain_device *);
> -int sas_discover_end_dev(struct domain_device *);
>
> void sas_unregister_dev(struct asd_sas_port *port, struct domain_device *);
>
next prev parent reply other threads:[~2022-12-05 8:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 8:16 [PATCH 0/6] scsi: libsas: Some coding style fixes and cleanups Jason Yan
2022-12-04 8:16 ` [PATCH 1/6] scsi: libsas: move sas_get_ata_command_set() up to save the declaration Jason Yan
2022-12-05 8:45 ` John Garry
2022-12-08 6:36 ` Jason Yan
2022-12-04 8:16 ` [PATCH 2/6] scsi: libsas: delete wrapper function sas_discover_end_dev() Jason Yan
2022-12-05 8:57 ` John Garry [this message]
2022-12-08 6:56 ` Jason Yan
2022-12-04 8:16 ` [PATCH 3/6] scsi: libsas: rename sas_discover_sata() and related refactors Jason Yan
2022-12-04 8:16 ` [PATCH 4/6] scsi: libsas: remove useless dev_list delete in sas_ex_discover_end_dev() Jason Yan
2022-12-05 9:14 ` John Garry
2022-12-08 7:21 ` Jason Yan
2022-12-08 10:40 ` John Garry
2022-12-08 11:11 ` Jason Yan
2022-12-04 8:16 ` [PATCH 5/6] scsi: libsas: factor out sas_ata_add_dev() Jason Yan
2022-12-05 9:24 ` John Garry
2022-12-08 7:26 ` Jason Yan
2022-12-04 8:16 ` [PATCH 6/6] scsi: libsas: factor out sas_ex_add_dev() Jason Yan
2022-12-05 9:31 ` John Garry
2022-12-08 8:07 ` 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=8729c1c5-c306-1fdc-ff30-174740be97c4@oracle.com \
--to=john.g.garry@oracle.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=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