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, 15 Jul 2021 16:12:51 +0200 [thread overview]
Message-ID: <YPBCY6IjDBwYTceO@infradead.org> (raw)
The following changes since commit a731763fc479a9c64456e0643d0ccf64203100c9:
blk-cgroup: prevent rcu_sched detected stalls warnings while iterating blkgs (2021-07-07 09:36:36 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.14-2021-07-15
for you to fetch changes up to 251ef6f71be2adfd09546a26643426fe62585173:
nvme-pci: do not call nvme_dev_remove_admin from nvme_remove (2021-07-13 12:03:20 +0200)
----------------------------------------------------------------
nvme fixes for Linux 5.14
- fix various races in nvme-pci when shutting down just after probing
(Casey Chen)
- fix a net_device leak in nvme-tcp (Prabhakar Kushwaha)
----------------------------------------------------------------
Casey Chen (2):
nvme-pci: fix multiple races in nvme_setup_io_queues
nvme-pci: do not call nvme_dev_remove_admin from nvme_remove
Prabhakar Kushwaha (1):
nvme-tcp: use __dev_get_by_name instead dev_get_by_name for OPT_HOST_IFACE
drivers/nvme/host/pci.c | 67 ++++++++++++++++++++++++++++++++++++++++++-------
drivers/nvme/host/tcp.c | 4 +--
2 files changed, 59 insertions(+), 12 deletions(-)
next reply other threads:[~2021-07-15 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 14:12 Christoph Hellwig [this message]
2021-07-15 15:32 ` [GIT PULL] nvme fixes for Linux 5.14 Jens Axboe
2021-07-22 18:56 Christoph Hellwig
2021-07-22 20:25 ` 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=YPBCY6IjDBwYTceO@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).