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 6.0
Date: Thu, 1 Sep 2022 10:29:51 +0300 [thread overview]
Message-ID: <YxBfb38kb18Im/QB@infradead.org> (raw)
The following changes since commit 645b5ed871f408c9826a61276b97ea14048d439c:
Merge branch 'md-fixes' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into block-6.0 (2022-08-24 13:58:37 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.0-2022-09-01
for you to fetch changes up to 478814a5584197fa1fb18377653626e3416e7cd6:
nvmet-tcp: fix unhandled tcp states in nvmet_tcp_state_change() (2022-08-31 07:58:10 +0300)
----------------------------------------------------------------
nvme fixes for Linux 6.0
- error handling fix for the new auth code (Hannes Reinecke)
- fix unhandled tcp states in nvmet_tcp_state_change (Maurizio Lombardi)
- add NVME_QUIRK_BOGUS_NID for Lexar NM610 (Shyamin Ayesh)
----------------------------------------------------------------
Hannes Reinecke (1):
nvmet-auth: add missing goto in nvmet_setup_auth()
Maurizio Lombardi (1):
nvmet-tcp: fix unhandled tcp states in nvmet_tcp_state_change()
Shyamin Ayesh (1):
nvme-pci: add NVME_QUIRK_BOGUS_NID for Lexar NM610
drivers/nvme/host/pci.c | 2 ++
drivers/nvme/target/auth.c | 1 +
drivers/nvme/target/tcp.c | 3 +++
3 files changed, 6 insertions(+)
next reply other threads:[~2022-09-01 7:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 7:29 Christoph Hellwig [this message]
2022-09-01 14:11 ` [GIT PULL] nvme fixes for Linux 6.0 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2022-09-29 15:02 Christoph Hellwig
2022-09-29 15:10 ` Jens Axboe
2022-09-08 15:35 Christoph Hellwig
2022-09-08 16:20 ` Jens Axboe
2022-08-11 14:05 Christoph Hellwig
2022-08-11 14:38 ` 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=YxBfb38kb18Im/QB@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).