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.17
Date: Thu, 27 Jan 2022 08:19:22 +0100 [thread overview]
Message-ID: <YfJHeoRZIPt2t3aP@infradead.org> (raw)
The following changes since commit 83114df32ae779df57e0af99a8ba6c3968b2ba3d:
block: fix memory leak in disk_register_independent_access_ranges (2022-01-23 09:13:09 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.17-2022-01-27
for you to fetch changes up to a5f3851b7f7951e8d4ba0a9ba3b5308a5f250a2d:
nvme-fabrics: remove the unneeded ret variable in nvmf_dev_show (2022-01-27 08:17:17 +0100)
----------------------------------------------------------------
nvme fixes for Linux 5.17
- add the IGNORE_DEV_SUBNQN quirk for Intel P4500/P4600 SSDs (Wu Zheng)
- remove the unneeded ret variable in nvmf_dev_show (Changcheng Deng)
----------------------------------------------------------------
Changcheng Deng (1):
nvme-fabrics: remove the unneeded ret variable in nvmf_dev_show
Wu Zheng (1):
nvme-pci: add the IGNORE_DEV_SUBNQN quirk for Intel P4500/P4600 SSDs
drivers/nvme/host/fabrics.c | 3 +--
drivers/nvme/host/pci.c | 3 ++-
2 files changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2022-01-27 7:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 7:19 Christoph Hellwig [this message]
2022-01-27 13:53 ` [GIT PULL] nvme fixes for Linux 5.17 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2022-02-03 19:35 Christoph Hellwig
2022-02-03 19:38 ` Jens Axboe
2022-02-10 7:42 Christoph Hellwig
2022-02-10 13:57 ` Jens Axboe
2022-02-22 17:21 ` Christoph Hellwig
2022-02-22 17:26 ` Jens Axboe
2022-02-22 17:29 ` Christoph Hellwig
2022-02-24 7:33 Christoph Hellwig
2022-02-24 14:03 ` 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=YfJHeoRZIPt2t3aP@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.