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 fix for Linux 5.19
Date: Wed, 27 Jul 2022 11:54:31 -0400 [thread overview]
Message-ID: <YuFftyWcAMRP/NC5@infradead.org> (raw)
The following changes since commit 82e094f7bd988c02df27f8c8d81af8f750660b2a:
Merge branch 'md-fixes' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into block-5.19 (2022-07-19 12:42:33 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.19-2022-07-27
for you to fetch changes up to d6c52fa3e955b97f8eb3ac824d2a3e0af147b3ce:
nvme-pci: Crucial P2 has bogus namespace ids (2022-07-25 07:34:07 +0200)
----------------------------------------------------------------
nvme fix for Linux 5.19
- yet another duplicate ID quirk (Tobias Gruetzmacher)
----------------------------------------------------------------
Tobias Gruetzmacher (1):
nvme-pci: Crucial P2 has bogus namespace ids
drivers/nvme/host/pci.c | 2 ++
1 file changed, 2 insertions(+)
next reply other threads:[~2022-07-27 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 15:54 Christoph Hellwig [this message]
2022-07-27 16:04 ` [GIT PULL] nvme fix for Linux 5.19 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=YuFftyWcAMRP/NC5@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