From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <keith.busch@intel.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: [GIT PULL] nvme updates for 4.13-rc3
Date: Thu, 27 Jul 2017 15:30:11 +0200 [thread overview]
Message-ID: <20170727133011.2vyqepblk2oboit4@infradead.org> (raw)
Just a couple small fixes all over.
The following changes since commit 76451d79bde6bed17e113f057e58e1fa5fb79e78:
blk-mq: map queues to all present CPUs (2017-07-24 10:01:31 -0600)
are available in the git repository at:
git://git.infradead.org/nvme.git nvme-4.13
for you to fetch changes up to 7dd1ab163c17e11473a65b11f7e748db30618ebb:
nvme: validate admin queue before unquiesce (2017-07-26 17:41:41 +0200)
----------------------------------------------------------------
Christoph Hellwig (1):
nvme-pci: fix HMB size calculation
James Smart (2):
nvme-fc: address target disconnect race conditions in fcp io submit
nvme-fc: revise TRADDR parsing
Johannes Thumshirn (1):
nvme: also provide a UUID in the WWID sysfs attribute
Jon Derrick (1):
nvme: fabrics commands should use the fctype field for data direction
Scott Bauer (1):
nvme: validate admin queue before unquiesce
drivers/nvme/host/core.c | 6 ++-
drivers/nvme/host/fc.c | 121 +++++++++++++++++++++++++----------------------
drivers/nvme/host/pci.c | 6 +--
drivers/nvme/target/fc.c | 101 ++++++++++++++++++++-------------------
include/linux/nvme-fc.h | 19 ++++++++
include/linux/nvme.h | 2 +-
6 files changed, 145 insertions(+), 110 deletions(-)
next reply other threads:[~2017-07-27 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 13:30 Christoph Hellwig [this message]
2017-07-27 14:09 ` [GIT PULL] nvme updates for 4.13-rc3 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=20170727133011.2vyqepblk2oboit4@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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).