From: hch@infradead.org (Christoph Hellwig)
Subject: [GIT PULL] additional nvme fixes and cleanups for Linux 4.16
Date: Fri, 19 Jan 2018 20:02:19 +0100 [thread overview]
Message-ID: <20180119190219.cdsqnoiwe77j2zhd@infradead.org> (raw)
The following changes since commit bf9ae8c5325c0070d0ec81a849bba8d156f65993:
blk-mq: fix bad clear of RQF_MQ_INFLIGHT in blk_mq_ct_ctx_init() (2018-01-14 10:46:24 -0700)
are available in the git repository at:
git://git.infradead.org/nvme.git nvme-4.16
for you to fetch changes up to 88de4598bca84e27b261685c06fff816b8d932a1:
nvme-pci: clean up SMBSZ bit definitions (2018-01-17 17:55:14 +0100)
----------------------------------------------------------------
Christoph Hellwig (2):
nvme-pci: clean up CMB initialization
nvme-pci: clean up SMBSZ bit definitions
James Smart (2):
nvme-fc: fix rogue admin cmds stalling teardown
nvme-fc: correct hang in nvme_ns_remove()
Minwoo Im (1):
nvme: fix comment typos in nvme_create_io_queues
Roland Dreier (1):
nvme-fabrics: fix memory leak when parsing host ID option
Roy Shterman (1):
nvme: host delete_work and reset_work on separate workqueues
Sagi Grimberg (3):
nvme-pci: serialize pci resets
nvme-pci: allocate device queues storage space at probe
nvmet: release a ns reference in nvmet_req_uninit if needed
drivers/nvme/host/core.c | 47 ++++++++++++++--
drivers/nvme/host/fabrics.c | 4 +-
drivers/nvme/host/fc.c | 6 ++
drivers/nvme/host/nvme.h | 3 +
drivers/nvme/host/pci.c | 133 ++++++++++++++++++++------------------------
drivers/nvme/host/rdma.c | 2 +-
drivers/nvme/target/core.c | 3 +
drivers/nvme/target/loop.c | 2 +-
include/linux/nvme.h | 22 +++++---
9 files changed, 132 insertions(+), 90 deletions(-)
next reply other threads:[~2018-01-19 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 19:02 Christoph Hellwig [this message]
2018-01-19 19:29 ` [GIT PULL] additional nvme fixes and cleanups for Linux 4.16 Jens Axboe
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=20180119190219.cdsqnoiwe77j2zhd@infradead.org \
--to=hch@infradead.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