All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	linux-nvme@lists.infradead.org, Zhang Yi <yizhan@redhat.com>,
	linux-block@vger.kernel.org,
	Johannes Thumshirn <jthumshirn@suse.de>
Subject: Re: [PATCH v3 0/3] nvme: fix hang in path of removing disk
Date: Mon, 22 May 2017 20:48:12 +0200	[thread overview]
Message-ID: <20170522184812.GA1360@lst.de> (raw)
In-Reply-To: <20170522150505.452-1-ming.lei@redhat.com>

Thanks Ming,

I'll add the three patches to the nvme-4.12 queue, assuming Jens
is okay with us queueing up the block path to remove
blk_mq_abort_requeue_list.

WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH v3 0/3] nvme: fix hang in path of removing disk
Date: Mon, 22 May 2017 20:48:12 +0200	[thread overview]
Message-ID: <20170522184812.GA1360@lst.de> (raw)
In-Reply-To: <20170522150505.452-1-ming.lei@redhat.com>

Thanks Ming,

I'll add the three patches to the nvme-4.12 queue, assuming Jens
is okay with us queueing up the block path to remove
blk_mq_abort_requeue_list.

  parent reply	other threads:[~2017-05-22 18:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 15:05 [PATCH v3 0/3] nvme: fix hang in path of removing disk Ming Lei
2017-05-22 15:05 ` Ming Lei
2017-05-22 15:05 ` [PATCH v3 1/3] nvme: use blk_mq_start_hw_queues() in nvme_kill_queues() Ming Lei
2017-05-22 15:05   ` Ming Lei
2017-05-22 15:05 ` [PATCH v3 2/3] nvme: avoid to use blk_mq_abort_requeue_list() Ming Lei
2017-05-22 15:05   ` Ming Lei
2017-05-22 15:05 ` [PATCH v3 3/3] blk-mq: remove blk_mq_abort_requeue_list() Ming Lei
2017-05-22 15:05   ` Ming Lei
2017-05-22 18:48 ` Christoph Hellwig [this message]
2017-05-22 18:48   ` [PATCH v3 0/3] nvme: fix hang in path of removing disk 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=20170522184812.GA1360@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 \
    --cc=yizhan@redhat.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.