From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
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: Re: [GIT PULL] nvme fixes for Linux 6.15
Date: Thu, 17 Apr 2025 06:19:24 -0600 [thread overview]
Message-ID: <b84e959c-c8a9-4f73-aaad-5b905117e3af@kernel.dk> (raw)
In-Reply-To: <aACj5pg7dLAsfZ1u@infradead.org>
On 4/17/25 12:47 AM, Christoph Hellwig wrote:
> 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)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2025-04-17 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 6:47 [GIT PULL] nvme fixes for Linux 6.15 Christoph Hellwig
2025-04-17 12:19 ` Jens Axboe [this message]
-- 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=b84e959c-c8a9-4f73-aaad-5b905117e3af@kernel.dk \
--to=axboe@kernel.dk \
--cc=axboe@fb.com \
--cc=hch@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox