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, resend] nvme updates for Linux 6.16
Date: Thu, 26 Jun 2025 07:33:50 -0600 [thread overview]
Message-ID: <3a148e8b-86a1-415d-b05f-237d40596d0d@kernel.dk> (raw)
In-Reply-To: <aF1H_345SuVYxoCW@infradead.org>
On 6/26/25 7:15 AM, Christoph Hellwig wrote:
> [note that the commit dates are very recent. That is because somehow the
> tree the ran through the build bot had me as the author for the commit
> from Keith, so I did a metadata only rebase just now to fix that]
>
> The following changes since commit 4c8a951787ffc4b61a547db9866196104971b5fd:
>
> ublk: setup ublk_io correctly in case of ublk_get_data() failure (2025-06-24 20:45:31 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.16-2025-06-26
>
> for you to fetch changes up to f46d273449ba65afd53f3dd8fe0182c9df877e08:
>
> nvme: fix atomic write size validation (2025-06-26 13:04:37 +0200)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.16
>
> - reset delayed remove_work after reconnect (Keith Busch)
> - fix atomic write size validation (Christoph Hellwig)
Pulled, thanks.
--
Jens Axboe
prev parent reply other threads:[~2025-06-26 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 13:15 [GIT PULL, resend] nvme updates for Linux 6.16 Christoph Hellwig
2025-06-26 13:33 ` Jens Axboe [this message]
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=3a148e8b-86a1-415d-b05f-237d40596d0d@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).