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 updates for Linux 6.17
Date: Thu, 31 Jul 2025 10:55:44 -0600 [thread overview]
Message-ID: <fdd15ad1-a1e6-4e22-9cef-0dfce1f8b24d@kernel.dk> (raw)
In-Reply-To: <aIt40gBo9MuyC9Y2@infradead.org>
On 7/31/25 8:08 AM, Christoph Hellwig wrote:
> The following changes since commit 5421681bc3ef13476bd9443379cd69381e8760fa:
>
> blk-ioc: don't hold queue_lock for ioc_lookup_icq() (2025-07-29 06:26:34 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.17-2025-07-31
>
> for you to fetch changes up to 367c240b0a99c7ada700a44345dd3144a02b6164:
>
> nvme: fix various comment typos (2025-07-31 06:35:58 -0700)
>
> ----------------------------------------------------------------
> nvme updates for Linux 6.17
>
> - add support for getting the FDP featuee in fabrics passthru path
> (Nitesh Shetty)
> - add capability to connect to an administrative controller
> (Kamaljit Singh)
> - fix a leak on sgl setup error (Keith Busch)
> - initialize discovery subsys after debugfs is initialized
> (Mohamed Khalfella)
> - fix various comment typos (Bjorn Helgaas)
> - remove unneeded semicolons (Jiapeng Chong)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2025-07-31 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-31 14:08 [GIT PULL] nvme updates for Linux 6.17 Christoph Hellwig
2025-07-31 16:55 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-22 6:04 Christoph Hellwig
2025-07-22 10:55 ` 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=fdd15ad1-a1e6-4e22-9cef-0dfce1f8b24d@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;
as well as URLs for NNTP newsgroup(s).