From: Bart Van Assche <bart.vanassche@sandisk.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Christoph Hellwig <hch@lst.de>,
Johannes Thumshirn <jthumshirn@suse.de>,
Dan Williams <dan.j.williams@intel.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2/2] Restart list search after unlock in scsi_remove_target
Date: Wed, 4 Nov 2015 15:20:14 -0800 [thread overview]
Message-ID: <563A92AE.5000605@sandisk.com> (raw)
In-Reply-To: <1446677072.2216.30.camel@HansenPartnership.com>
On 11/04/2015 02:44 PM, James Bottomley wrote:
> On Wed, 2015-11-04 at 14:35 -0800, Bart Van Assche wrote:
>> (replying to my own e-mail)
>>
>> Hello Christoph,
>>
>> Is it OK for you if I mention you as author of this e-mail ?
>
> Could you just both co-operate, especially since there's not much
> difference between the patches.
Hello James and Christoph,
Patch [2/2] is identical to the patch Christoph had posted except that
it has been rebased on top of patch [1/2] of this series. I will be
happy to step back if Christoph or someone else wants to take the lead
here. The only reason I started looking into this is that there was no
further progress on the original e-mail thread about this subject
(http://thread.gmane.org/gmane.linux.kernel/2052359).
Bart.
next prev parent reply other threads:[~2015-11-04 23:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 22:06 [PATCH 0/2] Fix a hard lockup in scsi_remove_target() Bart Van Assche
2015-10-30 22:08 ` [PATCH 1/2] Separate target visibility from reaped state information Bart Van Assche
2015-11-05 8:50 ` Christoph Hellwig
2015-10-30 22:09 ` [PATCH 2/2] Restart list search after unlock in scsi_remove_target Bart Van Assche
2015-11-04 22:35 ` Bart Van Assche
2015-11-04 22:44 ` James Bottomley
2015-11-04 23:20 ` Bart Van Assche [this message]
2015-11-16 17:57 ` Christoph Hellwig
2015-11-05 16:55 ` Dan Williams
2015-11-05 17:05 ` James Bottomley
2015-11-05 8:51 ` Christoph Hellwig
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=563A92AE.5000605@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=linux-scsi@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.