From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>, Keith Busch <keith.busch@intel.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Johannes Thumshirn <jthumshirn@suse.de>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: Re: [PATCH] nvme: fix hang in remove path
Date: Mon, 5 Jun 2017 10:20:55 +0200 [thread overview]
Message-ID: <20170605082055.GA22375@lst.de> (raw)
In-Reply-To: <20170602083208.4518-1-ming.lei@redhat.com>
Thanks Ming, I'll add this to the nvme tree for 4.12-rc.
prev parent reply other threads:[~2017-06-05 8:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 8:32 [PATCH] nvme: fix hang in remove path Ming Lei
2017-06-02 13:36 ` Sagi Grimberg
2017-06-02 18:04 ` Rakesh Pandit
2017-06-04 15:24 ` Sagi Grimberg
2017-06-05 8:44 ` Rakesh Pandit
2017-06-05 8:47 ` Rakesh Pandit
2017-06-05 19:45 ` Rakesh Pandit
2017-06-06 7:10 ` Sagi Grimberg
2017-06-06 7:12 ` Christoph Hellwig
2017-06-06 7:30 ` Rakesh Pandit
2017-06-05 8:20 ` Christoph Hellwig [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=20170605082055.GA22375@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=jthumshirn@suse.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=ming.lei@redhat.com \
--cc=sagi@grimberg.me \
/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).