From: Sagi Grimberg <sagi@grimberg.me>
To: Bart Van Assche <bart.vanassche@wdc.com>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Keith Busch <keith.busch@intel.com>,
Matias Bjorling <mb@lightnvm.io>,
stable@vger.kernel.org
Subject: Re: [PATCH v2 2/2] nvme: Fix race conditions related to creation of /dev/nvme0n<x>
Date: Fri, 17 Aug 2018 14:58:44 -0700 [thread overview]
Message-ID: <5558c7ba-c0bd-c532-bd62-765c255263e7@grimberg.me> (raw)
In-Reply-To: <20180813172531.7451-3-bart.vanassche@wdc.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
prev parent reply other threads:[~2018-08-18 1:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180813172531.7451-1-bart.vanassche@wdc.com>
2018-08-13 17:25 ` [PATCH v2 1/2] block: Introduce alloc_disk_node_attr() Bart Van Assche
2018-08-13 18:52 ` Greg Kroah-Hartman
2018-08-13 17:25 ` [PATCH v2 2/2] nvme: Fix race conditions related to creation of /dev/nvme0n<x> Bart Van Assche
2018-08-17 21:58 ` Sagi Grimberg [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=5558c7ba-c0bd-c532-bd62-765c255263e7@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@wdc.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=mb@lightnvm.io \
--cc=stable@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 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).