From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: [GIT PULL] nvme fixes for Linux 6.0
Date: Thu, 29 Sep 2022 17:02:28 +0200 [thread overview]
Message-ID: <YzWzhIAX+vtSmo39@infradead.org> (raw)
The following changes since commit 4c66a326b5ab784cddd72de07ac5b6210e9e1b06:
Revert "block: freeze the queue earlier in del_gendisk" (2022-09-20 08:15:44 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.0-2022-09-29
for you to fetch changes up to d14c273132aec81a1a8107c9ab4865b89e7910a7:
nvme-pci: disable Write Zeroes on Phison E3C/E4C (2022-09-27 09:20:30 +0200)
----------------------------------------------------------------
nvme fixes for Linux 6.1
- fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for nvme devices
(Michael Kelley)
- disable Write Zeroes on Phison E3C/E4C (Tina Hsu)
----------------------------------------------------------------
Michael Kelley (1):
nvme: Fix IOC_PR_CLEAR and IOC_PR_RELEASE ioctls for nvme devices
Tina Hsu (1):
nvme-pci: disable Write Zeroes on Phison E3C/E4C
drivers/nvme/host/core.c | 6 +++---
drivers/nvme/host/pci.c | 4 ++++
2 files changed, 7 insertions(+), 3 deletions(-)
next reply other threads:[~2022-09-29 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 15:02 Christoph Hellwig [this message]
2022-09-29 15:10 ` [GIT PULL] nvme fixes for Linux 6.0 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2022-09-08 15:35 Christoph Hellwig
2022-09-08 16:20 ` Jens Axboe
2022-09-01 7:29 Christoph Hellwig
2022-09-01 14:11 ` Jens Axboe
2022-08-11 14:05 Christoph Hellwig
2022-08-11 14:38 ` 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=YzWzhIAX+vtSmo39@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.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).