From: keith.busch@intel.com (Keith Busch)
Subject: [GIT PULL] nvme fixes for 4.16-rc4
Date: Wed, 28 Feb 2018 12:15:04 -0700 [thread overview]
Message-ID: <20180228191503.GI16002@localhost.localdomain> (raw)
The following changes since commit af27d9403f5b80685b79c88425086edccecaf711:
mm: hide a #warning for COMPILE_TEST (2018-02-16 09:41:36 -0800)
are available in the Git repository at:
git://git.infradead.org/nvme.git for-jens
for you to fetch changes up to bffd2b61670feef18d2535e9b53364d270a1c991:
nvmet: fix PSDT field check in command format (2018-02-28 10:10:22 -0700)
----------------------------------------------------------------
Baegjae Sung (1):
nvme-multipath: fix sysfs dangerously created links
Christoph Hellwig (3):
nvme-fabrics: don't check for non-NULL module in nvmf_register_transport
nvme-rdma: use blk_rq_payload_bytes instead of blk_rq_bytes
nvmet-loop: use blk_rq_payload_bytes for sgl selection
Jianchao Wang (1):
nvme-pci: Fix nvme queue cleanup if IRQ setup fails
Max Gurtovoy (1):
nvmet: fix PSDT field check in command format
drivers/nvme/host/core.c | 12 +++---------
drivers/nvme/host/fabrics.c | 2 +-
drivers/nvme/host/multipath.c | 15 ++++++++++-----
drivers/nvme/host/pci.c | 5 ++++-
drivers/nvme/host/rdma.c | 4 ++--
drivers/nvme/target/core.c | 9 ++++++---
drivers/nvme/target/loop.c | 4 ++--
7 files changed, 28 insertions(+), 23 deletions(-)
next reply other threads:[~2018-02-28 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 19:15 Keith Busch [this message]
2018-02-28 19:23 ` [GIT PULL] nvme fixes for 4.16-rc4 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=20180228191503.GI16002@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 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.