From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-block@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
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: Tue, 22 Jul 2025 04:55:07 -0600 [thread overview]
Message-ID: <252e6af4-7024-4805-807f-ac8407808c24@kernel.dk> (raw)
In-Reply-To: <aH8qCeSvpt3eH5g_@infradead.org>
On 7/22/25 12:04 AM, Christoph Hellwig wrote:
> The following changes since commit ab17ead0e0ee8650cd1cf4e481b1ed0ee9731956:
>
> block: fix blk_zone_append_update_request_bio() kernel-doc (2025-07-16 10:02:18 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.17-2025-07-22
>
> for you to fetch changes up to 5b2c214a95942f7997d1916a4c44017becbc3cac:
>
> nvme-pci: try function level reset on init failure (2025-07-17 17:46:33 +0200)
>
> ----------------------------------------------------------------
> nvme updates for Linux 6.17
>
> - try PCIe function level reset on init failure (Keith Busch)
> - log TLS handshake failures at error level (Maurizio Lombardi)
> - pci-epf: do not complete commands twice if nvmet_req_init() fails
> (Rick Wertenbroek)
> - misc cleanups (Alok Tiwari)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2025-07-22 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 6:04 [GIT PULL] nvme updates for Linux 6.17 Christoph Hellwig
2025-07-22 10:55 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-31 14:08 Christoph Hellwig
2025-07-31 16: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=252e6af4-7024-4805-807f-ac8407808c24@kernel.dk \
--to=axboe@kernel.dk \
--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