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>, <linux-kernel@vger.kernel.org>,
<john.garry@huawei.com>, <chenweilong@huawei.com>,
<zhaohongjiang@huawei.com>, <hare@suse.com>,
<dan.j.williams@intel.com>, <jthumshirn@suse.de>,
<Raj.Dinesh@microsemi.com>, <hch@lst.de>,
<huangdaode@hisilicon.com>, <chenxiang66@hisilicon.com>
Subject: Re: [PATCH v4 00/11] Enhance libsas hotplug feature
Date: Fri, 15 Sep 2017 21:43:45 -0400 [thread overview]
Message-ID: <yq1zi9vs9im.fsf@oracle.com> (raw)
In-Reply-To: <1504689314-20072-1-git-send-email-yanaijie@huawei.com> (Jason Yan's message of "Wed, 6 Sep 2017 17:15:03 +0800")
Jason,
> Yijing Wang handed over this topic to me. We are working on it the
> last two months. We have tested the patchset for a long time. Here is
> the new version.
Applied patches 1-4 and 11 to 4.15/scsi-queue. I suggest you resubmit
the rest to get them back on people's radar.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2017-09-16 1:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 9:15 [PATCH v4 00/11] Enhance libsas hotplug feature Jason Yan
2017-09-06 9:15 ` [PATCH v4 01/11] libsas: kill useless ha_event and do some cleanup Jason Yan
2017-09-06 12:38 ` Johannes Thumshirn
2017-09-06 13:20 ` Christoph Hellwig
2017-09-06 9:15 ` [PATCH v4 02/11] libsas: remove the numbering for each event enum Jason Yan
2017-09-06 12:41 ` Johannes Thumshirn
2017-09-06 13:20 ` Christoph Hellwig
2017-09-06 9:15 ` [PATCH v4 03/11] libsas: remove unused port_gone_completion and DISCE_PORT_GONE Jason Yan
2017-09-06 12:43 ` Johannes Thumshirn
2017-09-06 13:21 ` Christoph Hellwig
2017-09-06 9:15 ` [PATCH v4 04/11] libsas: rename notify_port_event() for consistency Jason Yan
2017-09-06 12:44 ` Johannes Thumshirn
2017-09-06 13:21 ` Christoph Hellwig
2017-09-06 9:15 ` [PATCH v4 05/11] libsas: Use dynamic alloced work to avoid sas event lost Jason Yan
2017-09-07 8:22 ` Jack Wang
2017-09-06 9:15 ` [PATCH v4 06/11] libsas: shut down the PHY if events reached the threshold Jason Yan
2017-09-06 9:15 ` [PATCH v4 07/11] libsas: make the event threshold configurable Jason Yan
2017-09-07 8:15 ` Jack Wang
2017-09-06 9:15 ` [PATCH v4 08/11] libsas: Use new workqueue to run sas event and disco event Jason Yan
2017-09-06 9:15 ` [PATCH v4 09/11] libsas: libsas: use flush_workqueue to process disco events synchronously Jason Yan
2017-09-06 9:15 ` [PATCH v4 10/11] libsas: direct call probe and destruct Jason Yan
2017-09-06 9:15 ` [PATCH v4 11/11] libsas: add event to defer list tail instead of head when draining Jason Yan
2017-09-06 13:21 ` Christoph Hellwig
2017-09-06 13:07 ` [PATCH v4 00/11] Enhance libsas hotplug feature John Garry
2017-09-06 13:22 ` Christoph Hellwig
2017-09-07 1:15 ` Jason Yan
2017-09-16 1:43 ` Martin K. Petersen [this message]
2017-09-18 12:54 ` 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=yq1zi9vs9im.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=Raj.Dinesh@microsemi.com \
--cc=chenweilong@huawei.com \
--cc=chenxiang66@hisilicon.com \
--cc=dan.j.williams@intel.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=huangdaode@hisilicon.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=john.garry@huawei.com \
--cc=jthumshirn@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=yanaijie@huawei.com \
--cc=zhaohongjiang@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