From: Bart Van Assche <bart.vanassche@sandisk.com>
To: James Bottomley <james.bottomley@hansenpartnership.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@suse.de>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] Fix a bdi reregistration race, v3
Date: Thu, 5 May 2016 12:58:39 -0700 [thread overview]
Message-ID: <572BA5EF.6000702@sandisk.com> (raw)
In-Reply-To: <56F9A22F.7020002@sandisk.com>
On 03/28/2016 02:29 PM, Bart Van Assche wrote:
> Avoid that the sd driver registers a BDI device with a name that
> is still in use. This patch avoids that the following warning gets
> triggered:
>
> [ ... ]
(replying to my own e-mail)
If anyone could review this patch that would be very welcome.
Thanks,
Bart.
next prev parent reply other threads:[~2016-05-05 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 21:29 [PATCH] Fix a bdi reregistration race, v3 Bart Van Assche
2016-05-05 19:58 ` Bart Van Assche [this message]
2016-05-05 20:40 ` Joe Lawrence
2016-05-09 13:50 ` Joe Lawrence
2016-06-03 23:25 ` Bart Van Assche
2016-06-15 10:49 ` Bart Van Assche
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=572BA5EF.6000702@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox