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] third round of nvme updates for Linux 5.13
Date: Thu, 22 Apr 2021 16:15:12 +0200 [thread overview]
Message-ID: <YIGE8ORkKryOdxtE@infradead.org> (raw)
The following changes since commit b777f4c47781df6b23e3f4df6fdb92d9aceac7bb:
ataflop: fix off by one in ataflop_probe() (2021-04-21 09:15:27 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.13-2021-04-22
for you to fetch changes up to 2637baed78010eeaae274feb5b99ce90933fadfb:
nvme: introduce generic per-namespace chardev (2021-04-22 07:25:17 +0200)
----------------------------------------------------------------
- add support for a per-namespace character device (Minwoo Im)
- various KATO fixes and cleanups (Hou Pu, Hannes Reinecke)
- APST fix and cleanup
----------------------------------------------------------------
Christoph Hellwig (2):
nvme: do not try to reconfigure APST when the controller is not live
nvme: cleanup nvme_configure_apst
Hannes Reinecke (2):
nvme: sanitize KATO setting
nvme: add 'kato' sysfs attribute
Hou Pu (1):
nvmet: avoid queuing keep-alive timer if it is disabled
Minwoo Im (1):
nvme: introduce generic per-namespace chardev
drivers/nvme/host/core.c | 258 +++++++++++++++++++++++++++-------------
drivers/nvme/host/fabrics.c | 4 +-
drivers/nvme/host/ioctl.c | 38 +++++-
drivers/nvme/host/multipath.c | 51 +++++++-
drivers/nvme/host/nvme.h | 14 ++-
drivers/nvme/target/admin-cmd.c | 10 +-
6 files changed, 276 insertions(+), 99 deletions(-)
next reply other threads:[~2021-04-22 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 14:15 Christoph Hellwig [this message]
2021-04-22 16:24 ` [GIT PULL] third round of nvme updates for Linux 5.13 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=YIGE8ORkKryOdxtE@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).