From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: John Garry <john.garry@huawei.com>
Cc: <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
wangyijing <wangyijing@huawei.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
<john.garry2@mail.dcu.ie>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
<linuxarm@huawei.com>, <lindar_liu@usish.com>,
Tejun Heo <tj@kernel.org>, <jinpu.wang@profitbricks.com>
Subject: Re: [RFC PATCH] scsi: libsas: fix WARN on device removal
Date: Thu, 17 Nov 2016 20:51:22 -0500 [thread overview]
Message-ID: <yq1inrl7dyd.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <9bdd2ca5-aa72-6a18-b66d-8e791e4852c7@huawei.com> (John Garry's message of "Thu, 17 Nov 2016 15:23:32 +0000")
>>>>> "John" == John Garry <john.garry@huawei.com> writes:
John> @Maintainers, would you be willing to accept this patch as an
John> interim fix for the dastardly WARN while we try to fix the flutter
John> issue?
I'll defer to James since I don't have much libsas experience.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-11-18 1:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 14:58 [RFC PATCH] scsi: libsas: fix WARN on device removal John Garry
2016-11-09 12:28 ` John Garry
2016-11-09 17:36 ` John Garry
2016-11-09 19:09 ` Dan Williams
2016-11-09 20:35 ` Dan Williams
2016-11-10 11:53 ` John Garry
2016-11-11 8:12 ` wangyijing
2016-11-11 8:23 ` John Garry
2016-11-11 8:49 ` wangyijing
2016-11-17 15:23 ` John Garry
2016-11-18 1:51 ` Martin K. Petersen [this message]
2016-11-18 1:53 ` Dan Williams
2016-11-18 9:00 ` John Garry
2016-11-18 19:08 ` Dan Williams
2016-11-21 15:16 ` John Garry
2016-11-21 17:13 ` Dan Williams
2016-11-22 16:56 ` John Garry
2016-11-23 1:07 ` wangyijing
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=yq1inrl7dyd.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=jinpu.wang@profitbricks.com \
--cc=john.garry2@mail.dcu.ie \
--cc=john.garry@huawei.com \
--cc=lindar_liu@usish.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=tj@kernel.org \
--cc=wangyijing@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).