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.18
Date: Fri, 15 Apr 2022 07:01:09 +0200 [thread overview]
Message-ID: <Ylj8FUYefzczGF92@infradead.org> (raw)
The following changes since commit 3e3876d322aef82416ecc496a4d4a587e0fdf7a3:
block: null_blk: end timed out poll request (2022-04-14 10:16:33 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.18-2022-04-15
for you to fetch changes up to 66dd346b84d79fde20832ed691a54f4881eac20d:
nvme-pci: disable namespace identifiers for Qemu controllers (2022-04-15 06:56:17 +0200)
----------------------------------------------------------------
nvme fixes for Linux 5.18
- tone down the error logging added this merge window a bit
(Chaitanya Kulkarni)
- quirk devices with non-unique unique identifiers (me)
----------------------------------------------------------------
Chaitanya Kulkarni (1):
nvme: don't print verbose errors for internal passthrough requests
Christoph Hellwig (3):
nvme: add a quirk to disable namespace identifiers
nvme-pci: disable namespace identifiers for the MAXIO MAP1002/1202
nvme-pci: disable namespace identifiers for Qemu controllers
drivers/nvme/host/core.c | 27 ++++++++++++++++++++-------
drivers/nvme/host/nvme.h | 5 +++++
drivers/nvme/host/pci.c | 9 ++++++++-
3 files changed, 33 insertions(+), 8 deletions(-)
next reply other threads:[~2022-04-15 5:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 5:01 Christoph Hellwig [this message]
2022-04-15 12:34 ` [GIT PULL] nvme fixes for Linux 5.18 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2022-03-29 7:31 Christoph Hellwig
2022-03-29 12:24 ` 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=Ylj8FUYefzczGF92@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