From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for Linux 5.14
Date: Thu, 22 Jul 2021 20:56:48 +0200 [thread overview]
Message-ID: <YPm/cHUBGJpVOS4n@infradead.org> (raw)
The following changes since commit ec645dc96699ea6c37b6de86c84d7288ea9a4ddf:
block: increase BLKCG_MAX_POLS (2021-07-17 13:07:24 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.14-2021-07-22
for you to fetch changes up to aaeb7bb061be545251606f4d9c82d710ca2a7c8e:
nvme: set the PRACT bit when using Write Zeroes with T10 PI (2021-07-21 17:24:10 +0200)
----------------------------------------------------------------
nvme fixes for Linux 5.14:
- tracing fix (Keith Busch)
- fix multipath head refcounting (Hannes Reinecke)
- Write Zeroes vs PI fix (me)
- drop a bogus WARN_ON (Zhihao Cheng)
----------------------------------------------------------------
Christoph Hellwig (1):
nvme: set the PRACT bit when using Write Zeroes with T10 PI
Hannes Reinecke (1):
nvme: fix refcounting imbalance when all paths are down
Keith Busch (1):
nvme: fix nvme_setup_command metadata trace event
Zhihao Cheng (1):
nvme-pci: don't WARN_ON in nvme_reset_work if ctrl.state is not RESETTING
drivers/nvme/host/core.c | 19 +++++++++++++++----
drivers/nvme/host/multipath.c | 9 ++++++++-
drivers/nvme/host/nvme.h | 11 ++---------
drivers/nvme/host/pci.c | 4 +++-
drivers/nvme/host/trace.h | 6 +++---
5 files changed, 31 insertions(+), 18 deletions(-)
next reply other threads:[~2021-07-22 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 18:56 Christoph Hellwig [this message]
2021-07-22 20:25 ` [GIT PULL] nvme fixes for Linux 5.14 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-07-15 14:12 Christoph Hellwig
2021-07-15 15:32 ` 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=YPm/cHUBGJpVOS4n@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--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).