From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jason Yan <yanaijie@huawei.com>
Cc: <martin.petersen@oracle.com>, <jejb@linux.vnet.ibm.com>,
<linux-scsi@vger.kernel.org>, <john.garry@huawei.com>
Subject: Re: [PATCH v3] scsi: libsas: stop discovering if oob mode is disconnected
Date: Mon, 09 Dec 2019 19:16:26 -0500 [thread overview]
Message-ID: <yq1blshox0l.fsf@oracle.com> (raw)
In-Reply-To: <20191206011118.46909-1-yanaijie@huawei.com> (Jason Yan's message of "Fri, 6 Dec 2019 09:11:18 +0800")
Jason,
> The discovering of sas port is driven by workqueue in libsas. When
> libsas is processing port events or phy events in workqueue, new
> events may rise up and change the state of some structures such as
> asd_sas_phy.
Applied to 5.5/scsi-fixes, thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-12-10 0:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 1:11 [PATCH v3] scsi: libsas: stop discovering if oob mode is disconnected Jason Yan
2019-12-10 0:16 ` Martin K. Petersen [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=yq1blshox0l.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-scsi@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).