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, 1 May 2025 07:56:28 -0600 [thread overview]
Message-ID: <9e4e6afb-6b91-431c-8deb-aedf2f9e3a43@kernel.dk> (raw)
In-Reply-To: <aBN4IW2wlSfRIfjU@infradead.org>
On 5/1/25 7:33 AM, Christoph Hellwig wrote:
> The following changes since commit a584b2630b0d31f8a20e4ccb4de370b160177b8a:
>
> ublk: remove the check of ublk_need_req_ref() from __ublk_check_and_get_req (2025-04-29 06:01:36 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.15-2025-05-01
>
> for you to fetch changes up to 8edb86b2ed1d63cc400aecae8eb8c8114837171a:
>
> nvmet-auth: always free derived key data (2025-04-30 08:09:09 -0500)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.15
>
> - fix queue unquiesce check on PCI slot_reset (Keith Busch)
> - fix premature queue removal and I/O failover in nvme-tcp
> (Michael Liang)
> - don't restore null sk_state_change (Alistair Francis)
> - select CONFIG_TLS where needed (Alistair Francis)
> - always free derived key data (Hannes Reinecke)
> - more quirks (Wentao Guan)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2025-05-01 13:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-01 13:33 [GIT PULL] nvme fixes for Linux 6.15 Christoph Hellwig
2025-05-01 13:56 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-15 11:56 Christoph Hellwig
2025-05-15 12:21 ` Jens Axboe
2025-05-08 15:07 Christoph Hellwig
2025-05-08 15:14 ` Jens Axboe
2025-04-24 11:23 hch
2025-04-24 12:28 ` Jens Axboe
2025-04-17 6:47 Christoph Hellwig
2025-04-17 12: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=9e4e6afb-6b91-431c-8deb-aedf2f9e3a43@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