From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for Linux 6.15
Date: Thu, 17 Apr 2025 08:47:02 +0200 [thread overview]
Message-ID: <aACj5pg7dLAsfZ1u@infradead.org> (raw)
The following changes since commit 0b7a4817756c7906d0a8112c953ce88d7cd8d4c6:
ublk: don't suggest CONFIG_BLK_DEV_UBLK=Y (2025-04-15 18:59:33 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.15-2025-04-17
for you to fetch changes up to ad91308d3bdeb9d90ef4a400f379ce461f0fb6a7:
nvmet: pci-epf: cleanup link state management (2025-04-16 07:37:37 +0200)
----------------------------------------------------------------
nvme fixes for Linux 6.15
- fix scan failure for non-ANA multipath controllers (Hannes Reinecke)
- fix multipath sysfs links creation for some cases (Hannes Reinecke)
- PCIe endpoint fixes (Damien Le Moal)
- use NULL instead of 0 in the auth code (Damien Le Moal)
----------------------------------------------------------------
Damien Le Moal (4):
nvmet: auth: use NULL to clear a pointer in nvmet_auth_sq_free()
nvmet: pci-epf: always fully initialize completion entries
nvmet: pci-epf: clear CC and CSTS when disabling the controller
nvmet: pci-epf: cleanup link state management
Hannes Reinecke (2):
nvme: fixup scan failure for non-ANA multipath controllers
nvme-multipath: sysfs links may not be created for devices
drivers/nvme/host/core.c | 2 +-
drivers/nvme/host/multipath.c | 14 +++----
drivers/nvme/target/auth.c | 2 +-
drivers/nvme/target/pci-epf.c | 88 ++++++++++++++++++++++++++++---------------
4 files changed, 67 insertions(+), 39 deletions(-)
next reply other threads:[~2025-04-17 6:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 6:47 Christoph Hellwig [this message]
2025-04-17 12:19 ` [GIT PULL] nvme fixes for Linux 6.15 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2025-04-24 11:23 hch
2025-04-24 12:28 ` Jens Axboe
2025-05-01 13:33 Christoph Hellwig
2025-05-01 13:56 ` Jens Axboe
2025-05-08 15:07 Christoph Hellwig
2025-05-08 15:14 ` Jens Axboe
2025-05-15 11:56 Christoph Hellwig
2025-05-15 12:21 ` 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=aACj5pg7dLAsfZ1u@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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.