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 5.11
Date: Thu, 21 Jan 2021 09:32:42 +0100 [thread overview]
Message-ID: <YAk8Kt/DRZ7T6WBl@infradead.org> (raw)
The following changes since commit b4f664252f51e119e9403ef84b6e9ff36d119510:
Merge tag 'nvme-5.11-2021-01-14' of git://git.infradead.org/nvme into block-5.11 (2021-01-14 15:17:33 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.11-2020-01-21
for you to fetch changes up to fa0732168fa1369dd089e5b06d6158a68229f7b7:
nvme-pci: fix error unwind in nvme_map_data (2021-01-20 18:56:33 +0100)
----------------------------------------------------------------
nvme fixes for 5.11:
- fix a status code in nvmet (Chaitanya Kulkarni)
- avoid double completions in nvme-rdma/nvme-tcp (Chao Leng)
- fix the CMB support to cope with NVMe 1.4 controllers (Klaus Jensen)
- fix PRINFO handling in the passthrough ioctl (Revanth Rajashekar)
- fix a double DMA unmap in nvme-pci
----------------------------------------------------------------
Chaitanya Kulkarni (1):
nvmet: set right status on error in id-ns handler
Chao Leng (2):
nvme-rdma: avoid request double completion for concurrent nvme_rdma_timeout
nvme-tcp: avoid request double completion for concurrent nvme_tcp_timeout
Christoph Hellwig (2):
nvme-pci: refactor nvme_unmap_data
nvme-pci: fix error unwind in nvme_map_data
Klaus Jensen (1):
nvme-pci: allow use of cmb on v1.4 controllers
Revanth Rajashekar (1):
nvme: check the PRINFO bit before deciding the host buffer length
drivers/nvme/host/core.c | 17 +++++-
drivers/nvme/host/pci.c | 119 +++++++++++++++++++++++++++-------------
drivers/nvme/host/rdma.c | 15 +++--
drivers/nvme/host/tcp.c | 14 +++--
drivers/nvme/target/admin-cmd.c | 8 ++-
include/linux/nvme.h | 6 ++
6 files changed, 129 insertions(+), 50 deletions(-)
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-01-21 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 8:32 Christoph Hellwig [this message]
2021-01-21 12:41 ` [GIT PULL] nvme fixes for 5.11 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-02-04 15:07 Christoph Hellwig
2021-02-04 15:25 ` Jens Axboe
2021-02-04 15:27 ` Christoph Hellwig
2021-01-28 18:56 Christoph Hellwig
2021-01-28 18:58 ` Jens Axboe
2021-01-14 19:29 Christoph Hellwig
2021-01-15 2:48 ` Jens Axboe
2021-01-07 17:42 Christoph Hellwig
2021-01-07 17:58 ` 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=YAk8Kt/DRZ7T6WBl@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