From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
James Bottomley <jbottomley@parallels.com>,
Hannes Reinecke <hare@suse.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Fix a bdi reregistration race, v2
Date: Mon, 28 Mar 2016 14:26:27 -0700 [thread overview]
Message-ID: <56F9A183.5060405@sandisk.com> (raw)
In-Reply-To: <20151201072315.GA12183@infradead.org>
On 11/30/2015 11:23 PM, Christoph Hellwig wrote:
> On Mon, Nov 30, 2015 at 05:18:50PM -0800, Bart Van Assche wrote:
>> Since the original patch caused a regression, please proceed with reverting
>> the original patch.
>>
>> Regarding this patch: is there anyone on the CC-list of this e-mail who can
>> review it ?
>
> I'm not too fond of the approach. I'd much prefer if SCSI would just
> release the dev_t later, similar to DM or MD.
(replying to an e-mail of four months ago)
Hello Christoph,
Sorry that it took so long but last week I finally found the time to
look further into this. I will post a third version of this patch.
Bart.
prev parent reply other threads:[~2016-03-28 21:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 22:13 [PATCH] Fix a bdi reregistration race, v2 Bart Van Assche
2015-11-20 22:13 ` Bart Van Assche
2015-11-20 22:43 ` Aaro Koskinen
2015-11-20 22:55 ` Bart Van Assche
2015-11-24 23:13 ` Christoph Hellwig
2015-11-24 23:13 ` Christoph Hellwig
2015-11-24 23:23 ` Bart Van Assche
2015-11-25 8:47 ` Christoph Hellwig
2015-11-25 8:47 ` Christoph Hellwig
2015-11-25 14:59 ` Bart Van Assche
2015-12-01 0:57 ` Martin K. Petersen
2015-12-01 1:18 ` Bart Van Assche
2015-12-01 1:18 ` Bart Van Assche
2015-12-01 7:23 ` Christoph Hellwig
2015-12-01 7:23 ` Christoph Hellwig
2016-03-28 21:26 ` Bart Van Assche [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=56F9A183.5060405@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--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 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.