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 1/2] scsi: libsas: Make sas_notify_{phy,port}_event() return void
Date: Thu, 24 Feb 2022 13:05:01 +0000 [thread overview]
Message-ID: <06714ce6-40cd-653d-4e5f-4bafee355035@huawei.com> (raw)
In-Reply-To: <014a69ed-7a99-2a67-fa3a-947d11601114@opensource.wdc.com>
On 24/02/2022 12:43, Damien Le Moal wrote:
> On 2/24/22 20:04, John Garry wrote:
>> Nobody checks the return codes, so make them return void. Indeed, if the
>> LLDD cannot send an event, nothing much can be done in the LLDD about it.
>
> It really sound like the LLDDs should be fixed to e.g. reset the adapter
> if things go south with these functions. No sure though.
But this is not an adapter fault. As an example of a scenario which we
could be dealing with, it may be that a phyup event occurs in the
adapter but libsas cannot allocate memory to process the event. There's
not much the adapter/LLDD can do about that (nor does do).
>
>>
>> Also remove prototype for sas_notify_phy_event() in sas_internal.h, which
>> should not be there.
>>
>> Signed-off-by: John Garry <john.garry@huawei.com>
>> Reviewed-by: Xiang Chen <chenxiang66@hisilicon.com>
>
> In any case, these changes do not make anything worse :)
Thanks,
>
> Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
>
next prev parent reply other threads:[~2022-02-24 13:05 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 [this message]
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
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=06714ce6-40cd-653d-4e5f-4bafee355035@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®