From: John Garry <john.garry@huawei.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>
Cc: <chenxiang66@hisilicon.com>, <linux-scsi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>
Subject: Re: [PATCH 2/2] scsi: libsas: Use bool for queue_work() return code
Date: Thu, 24 Feb 2022 13:07:44 +0000 [thread overview]
Message-ID: <93ca25b8-db43-3ce8-0923-3acad41d0856@huawei.com> (raw)
In-Reply-To: <4b107020-2494-2470-ba1b-c2000eae1355@opensource.wdc.com>
>> -int sas_queue_work(struct sas_ha_struct *ha, struct sas_work *sw)
>> +bool sas_queue_work(struct sas_ha_struct *ha, struct sas_work *sw)
>> {
>> /* it's added to the defer_q when draining so return succeed */
>> - int rc = 1;
>> + bool rc = true;
>>
>> if (!test_bit(SAS_HA_REGISTERED, &ha->state))
>> - return 0;
>> + return false;
>>
>> if (test_bit(SAS_HA_DRAINING, &ha->state)) {
>> /* add it to the defer list, if not already pending */
>> @@ -28,11 +28,11 @@ int sas_queue_work(struct sas_ha_struct *ha, struct sas_work *sw)
>> return rc;
>
> While at it, I would cleanup this function like this:
ok, fine
>
> diff --git a/drivers/scsi/libsas/sas_event.c
> b/drivers/scsi/libsas/sas_event.c
> index 3613b9b315bc..38e6e91aaf36 100644
> --- a/drivers/scsi/libsas/sas_event.c
> +++ b/drivers/scsi/libsas/sas_event.c
> @@ -12,20 +12,17 @@
>
> int sas_queue_work(struct sas_ha_struct *ha, struct sas_work *sw)
> {
> - /* it's added to the defer_q when draining so return succeed */
> - int rc = 1;
> -
> if (!test_bit(SAS_HA_REGISTERED, &ha->state))
> - return 0;
> + return false;
>
> if (test_bit(SAS_HA_DRAINING, &ha->state)) {
> /* add it to the defer list, if not already pending */
> if (list_empty(&sw->drain_node))
> list_add_tail(&sw->drain_node, &ha->defer_q);
> - } else
> - rc = queue_work(ha->event_q, &sw->work);
> + return true;
> + }
>
> - return rc;
> + return queue_work(ha->event_q, &sw->work);
> }
>
> No local variable :)
>
>> }
>>
>> -static int sas_queue_event(int event, struct sas_work *work,
>> +static bool sas_queue_event(int event, struct sas_work *work,
>> struct sas_ha_struct *ha)
>> {
>> unsigned long flags;
>> - int rc;
>> + bool rc;
>>
>> spin_lock_irqsave(&ha->lock, flags);
>> rc = sas_queue_work(ha, work);
>> @@ -44,13 +44,12 @@ static int sas_queue_event(int event, struct sas_work *work,
>> void sas_queue_deferred_work(struct sas_ha_struct *ha)
>> {
>> struct sas_work *sw, *_sw;
>> - int ret;
>>
>> spin_lock_irq(&ha->lock);
>> list_for_each_entry_safe(sw, _sw, &ha->defer_q, drain_node) {
>> list_del_init(&sw->drain_node);
>> - ret = sas_queue_work(ha, sw);
>> - if (ret != 1) {
>> +
>> + if (sas_queue_work(ha, sw) == false) {
>
> if (!sas_queue_work(ha, sw)) ?
ok, yeah, that's the pattern I see elsehwhere in the kernel
>
>> pm_runtime_put(ha->dev);
>> sas_free_event(to_asd_sas_event(&sw->work));
>> }
>> @@ -170,7 +169,6 @@ void sas_notify_port_event(struct asd_sas_phy *phy, enum port_event event,
>> {
>> struct sas_ha_struct *ha = phy->ha;
>> struct asd_sas_event *ev;
>> - int ret;
>>
>> BUG_ON(event >= PORT_NUM_EVENTS);
>>
>> @@ -186,8 +184,7 @@ void sas_notify_port_event(struct asd_sas_phy *phy, enum port_event event,
>> if (sas_defer_event(phy, ev))
>> return;
>>
>> - ret = sas_queue_event(event, &ev->work, ha);
>> - if (ret != 1) {
>> + if (sas_queue_event(event, &ev->work, ha) == false) {
>
> Same.
>
>> pm_runtime_put(ha->dev);
>> sas_free_event(ev);
>> }
>> @@ -199,7 +196,6 @@ void sas_notify_phy_event(struct asd_sas_phy *phy, enum phy_event event,
>> {
>> struct sas_ha_struct *ha = phy->ha;
>> struct asd_sas_event *ev;
>> - int ret;
>>
>> BUG_ON(event >= PHY_NUM_EVENTS);
>>
>> @@ -215,8 +211,7 @@ void sas_notify_phy_event(struct asd_sas_phy *phy, enum phy_event event,
>> if (sas_defer_event(phy, ev))
>> return;
>>
>> - ret = sas_queue_event(event, &ev->work, ha);
>> - if (ret != 1) {
>> + if (sas_queue_event(event, &ev->work, ha) == false) {
>
> And again.
>
ok, thanks
prev parent reply other threads:[~2022-02-24 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 11:04 [PATCH 0/2] scsi: libsas: Some minor improvements John Garry
2022-02-24 11:04 ` [PATCH 1/2] scsi: libsas: Make sas_notify_{phy,port}_event() return void John Garry
2022-02-24 12:43 ` Damien Le Moal
2022-02-24 13:05 ` John Garry
2022-02-24 11:04 ` [PATCH 2/2] scsi: libsas: Use bool for queue_work() return code John Garry
2022-02-24 12:49 ` Damien Le Moal
2022-02-24 13:07 ` John Garry [this message]
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=93ca25b8-db43-3ce8-0923-3acad41d0856@huawei.com \
--to=john.garry@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--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®