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.15
Date: Tue, 7 Sep 2021 16:10:03 +0200 [thread overview]
Message-ID: <YTdyu/Y/d9woHINJ@infradead.org> (raw)
The following changes since commit 1c500ad706383f1a6609e63d0b5d1723fd84dab9:
loop: reduce the loop_ctl_mutex scope (2021-09-03 22:14:40 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.15-2021-09-07
for you to fetch changes up to aff959c2840858d55d9ee155d555b3aa7e068b32:
nvme: update MAINTAINERS email address (2021-09-06 10:08:09 +0200)
----------------------------------------------------------------
nvme fixes for Linux 5.15
- fix nvmet command set reporting for passthrough controllers
(Adam Manzanares)
- updated
- update a MAINTAINERS email address (Chaitanya Kulkarni)
- set QUEUE_FLAG_NOWAIT for nvme-multipth (me)
- handle errors from add_disk() (Luis Chamberlain)
- update the keep alive interval when kato is modified (Tatsuya Sasaki)
- fix a buffer overrun in nvmet_subsys_attr_serial (Hannes Reinecke)
- do not reset transport on data digest errors in nvme-tcp (Daniel Wagner)
- only call synchronize_srcu when clearing current path (Daniel Wagner)
- revalidate paths during rescan (Hannes Reinecke)
----------------------------------------------------------------
Adam Manzanares (2):
nvme: move nvme_multi_css into nvme.h
nvmet: looks at the passthrough controller when initializing CAP
Chaitanya Kulkarni (1):
nvme: update MAINTAINERS email address
Christoph Hellwig (2):
nvme-multipath: set QUEUE_FLAG_NOWAIT
nvmet: return bool from nvmet_passthru_ctrl and nvmet_is_passthru_req
Daniel Wagner (2):
nvme-tcp: Do not reset transport on data digest errors
nvme: only call synchronize_srcu when clearing current path
Hannes Reinecke (2):
nvme-multipath: revalidate paths during rescan
nvmet: fixup buffer overrun in nvmet_subsys_attr_serial()
Luis Chamberlain (1):
nvme: add error handling support for add_disk()
Tatsuya Sasaki (1):
nvme: update keep alive interval when kato is modified
MAINTAINERS | 2 +-
drivers/nvme/host/core.c | 68 ++++++++++++++++++++++++++++++++++-------
drivers/nvme/host/multipath.c | 19 +++++++++++-
drivers/nvme/host/nvme.h | 10 ++++++
drivers/nvme/host/tcp.c | 22 ++++++++++---
drivers/nvme/target/admin-cmd.c | 2 +-
drivers/nvme/target/configfs.c | 5 +--
drivers/nvme/target/core.c | 10 +++---
drivers/nvme/target/nvmet.h | 11 ++++---
drivers/nvme/target/passthru.c | 14 +++++++--
10 files changed, 132 insertions(+), 31 deletions(-)
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-09-07 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 14:10 Christoph Hellwig [this message]
2021-09-07 14:37 ` [GIT PULL] nvme fixes for Linux 5.15 Jens Axboe
2021-09-15 13:49 Christoph Hellwig
2021-09-15 13:54 ` Jens Axboe
2021-09-24 6:36 Christoph Hellwig
2021-09-24 13:15 ` Jens Axboe
2021-10-14 13:05 Christoph Hellwig
2021-10-14 15:07 ` Jens Axboe
2021-10-28 14:25 Christoph Hellwig
2021-10-28 14:34 ` 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=YTdyu/Y/d9woHINJ@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).