From: keith.busch@intel.com (Busch, Keith)
Subject: [PATCH 8/9] nvme: remove dead controllers from a work item
Date: Fri, 23 Oct 2015 19:31:20 +0000 [thread overview]
Message-ID: <20151023193119.GA9022@localhost.localdomain> (raw)
In-Reply-To: <20151023145159.GA2986@localhost.localdomain>
On Fri, Oct 23, 2015@02:51:59PM +0000, Busch, Keith wrote:
> No worries, I'll take care of the rebase and resend for consideration.
Only a little painful. :)
I merged the linux-block for-4.4/integrity, for-4.4/reservations,
for-linus, and for-next, plus all of Christoph's recent NVMe with some
merge conflict fixups, plus a few of my own:
http://git.infradead.org/users/kbusch/linux-nvme.git
The tree is just a convience for me, but just linking it here in hopes
that it's useful. It was a forced push, so abandon older clones if
they exist.
My first merge like this. I hope I got the process "right", but I wouldn't
be surprised there was a smarter way to do it.
I will send out separate patches to the list for the ones that haven't
been reviewed yet. I'll also try to apply some of the other patches
from the list that seem to have been forgotten; the PPC IOMMU issue is
pretty important.
next prev parent reply other threads:[~2015-10-23 19:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 12:03 nvme abort and reset fixes Christoph Hellwig
2015-10-22 12:03 ` [PATCH 1/9] nvme: only add a controller to dev_list after it's been fully initialized Christoph Hellwig
2015-10-22 12:03 ` [PATCH 2/9] nvme: don't take the I/O queue q_lock in nvme_timeout Christoph Hellwig
2015-10-22 12:03 ` [PATCH 3/9] nvme: merge nvme_abort_req and nvme_timeout Christoph Hellwig
2015-10-22 12:03 ` [PATCH 4/9] nvme: do not restart the request timeout if we're resetting the controller Christoph Hellwig
2015-10-22 16:27 ` Busch, Keith
2015-10-22 16:30 ` Christoph Hellwig
2015-10-22 17:15 ` Busch, Keith
2015-10-22 18:17 ` Christoph Hellwig
2015-10-22 12:03 ` [PATCH 5/9] nvme: simplify resets Christoph Hellwig
2015-10-22 12:03 ` [PATCH 6/9] nvme: abort requests on the reqeueue list when shutting down a controller Christoph Hellwig
2015-10-22 14:44 ` Busch, Keith
2015-10-22 14:58 ` Christoph Hellwig
2015-10-22 15:16 ` Busch, Keith
2015-10-22 16:27 ` Christoph Hellwig
2015-10-22 12:03 ` [PATCH 7/9] nvme: merge probe_work and reset_work Christoph Hellwig
2015-10-22 12:03 ` [PATCH 8/9] nvme: remove dead controllers from a work item Christoph Hellwig
2015-10-22 18:10 ` Busch, Keith
2015-10-22 18:12 ` Christoph Hellwig
2015-10-22 20:36 ` Busch, Keith
2015-10-23 5:57 ` Christoph Hellwig
2015-10-23 14:51 ` Busch, Keith
2015-10-23 19:31 ` Busch, Keith [this message]
2015-10-22 12:03 ` [PATCH 9/9] nvme: switch abort_limit to an atomic_t 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=20151023193119.GA9022@localhost.localdomain \
--to=keith.busch@intel.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;
as well as URLs for NNTP newsgroup(s).