From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
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: [GIT PULL] nvme updates for Linux 6.16
Date: Thu, 26 Jun 2025 13:07:28 +0200 [thread overview]
Message-ID: <aF0p8PlTkmFvfDeW@infradead.org> (raw)
[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 dd2c18548964ae7ad48d208a765d909cd35448a1:
nvme: reset delayed remove_work after reconnect (2025-06-26 13:04:35 +0200)
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)
----------------------------------------------------------------
Christoph Hellwig (2):
nvme: refactor the atomic write unit detection
nvme: fix atomic write size validation
drivers/nvme/host/core.c | 83 ++++++++++++++++++++++--------------------------
drivers/nvme/host/nvme.h | 3 +-
2 files changed, 39 insertions(+), 47 deletions(-)
next reply other threads:[~2025-06-26 11:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 11:07 Christoph Hellwig [this message]
2025-06-26 12:09 ` [GIT PULL] nvme updates for Linux 6.16 Keith Busch
-- strict thread matches above, loose matches on Subject: below --
2025-06-05 9:34 Christoph Hellwig
2025-06-05 13:42 ` Jens Axboe
2025-05-20 16:02 Christoph Hellwig
2025-05-20 16:14 ` 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=aF0p8PlTkmFvfDeW@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--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