From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, Sagi Grimberg <sagi@grimberg.me>
Subject: [GIT PULL] nvme-5.4rc7
Date: Wed, 6 Nov 2019 07:31:17 +0900 [thread overview]
Message-ID: <20191105223117.GB890@redsun51.ssa.fujisawa.hgst.com> (raw)
Hi Jens,
We have a few late nvme fixes for a couple device removal kernel crashes,
and a compat fix for a new ioctl introduced during this merge window.
The following changes since commit 41591a51f00d2dc7bb9dc6e9bedf56c5cf6f2392:
iocost: don't nest spin_lock_irq in ioc_weight_write() (2019-10-31 11:40:57 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.4-rc7
for you to fetch changes up to 0d6eeb1fd625272bd60d25f2d5e116cf582fc7dc:
nvme: change nvme_passthru_cmd64 to explicitly mark rsvd (2019-11-06 06:17:38 +0900)
----------------------------------------------------------------
Anton Eidelman (1):
nvme-multipath: fix crash in nvme_mpath_clear_ctrl_paths
Charles Machalow (1):
nvme: change nvme_passthru_cmd64 to explicitly mark rsvd
Max Gurtovoy (1):
nvme-rdma: fix a segmentation fault during module unload
drivers/nvme/host/multipath.c | 2 ++
drivers/nvme/host/rdma.c | 8 ++++++++
include/uapi/linux/nvme_ioctl.h | 1 +
3 files changed, 11 insertions(+)
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2019-11-05 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 22:31 Keith Busch [this message]
2019-11-05 22:35 ` [GIT PULL] nvme-5.4rc7 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=20191105223117.GB890@redsun51.ssa.fujisawa.hgst.com \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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).