From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <keith.busch@intel.com>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] early nvme pull request for 5.1
Date: Mon, 4 Feb 2019 16:10:54 +0100 [thread overview]
Message-ID: <20190204151054.GA32678@infradead.org> (raw)
Hi Jens,
below is our current (small) queue of NVMe patches for Linux 5.1. We
want the re-addition of the Write Zeroes support to be in linu-next for
a few weeks as it caused some problems last time. The only other
patch is a cleanup from Sagi.
The following changes since commit bb94aea1444b9859faa8d72aff3713fcd11c6696:
blk-mq: save default hctx into ctx->hctxs for not-supported type (2019-02-01 08:33:43 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.1
for you to fetch changes up to 794a4cb3d2f7c105112f9b59525533f00ac06006:
nvme: remove the .stop_ctrl callout (2019-02-04 15:41:25 +0100)
----------------------------------------------------------------
Chaitanya Kulkarni (1):
nvme: add support for the Write Zeroes command
Sagi Grimberg (1):
nvme: remove the .stop_ctrl callout
drivers/nvme/host/core.c | 54 ++++++++++++++++++++++++++++++++++++++++++++----
drivers/nvme/host/nvme.h | 1 -
drivers/nvme/host/rdma.c | 12 +++--------
drivers/nvme/host/tcp.c | 10 +++------
4 files changed, 56 insertions(+), 21 deletions(-)
next reply other threads:[~2019-02-04 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 15:10 Christoph Hellwig [this message]
2019-02-04 18:28 ` [GIT PULL] early nvme pull request for 5.1 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=20190204151054.GA32678@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).