From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for Linux 6.18
Date: Thu, 16 Oct 2025 12:52:27 -0600 [thread overview]
Message-ID: <aPE-64L5715o7FlW@kbusch-mbp> (raw)
The following changes since commit 455281c0ef4e2cabdfe2e8b83fa6010d5210811c:
loop: remove redundant __GFP_NOWARN flag (2025-10-08 06:27:53 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.18-2025-10-16
for you to fetch changes up to 5a869d017793399fd1d2609ff27e900534173eb3:
nvme/tcp: handle tls partially sent records in write_space() (2025-10-16 11:32:04 -0700)
----------------------------------------------------------------
nvme fixes for Linux 6.18
- iostats accounting fixed on multipath retries (Amit)
- secure concatenation response fixup (Martin)
- tls partial record fixup (Wilfred)
----------------------------------------------------------------
Amit Chaudhary (1):
nvme-multipath: Skip nr_active increments in RETRY disposition
Martin George (1):
nvme-auth: update sc_c in host response
Wilfred Mallawa (1):
nvme/tcp: handle tls partially sent records in write_space()
drivers/nvme/host/auth.c | 6 +++++-
drivers/nvme/host/multipath.c | 6 ++++--
drivers/nvme/host/tcp.c | 3 +++
3 files changed, 12 insertions(+), 3 deletions(-)
next reply other threads:[~2025-10-16 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 18:52 Keith Busch [this message]
2025-10-17 1:47 ` [GIT PULL] nvme fixes for Linux 6.18 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2025-11-20 15:35 Keith Busch
2025-11-20 15:42 ` 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=aPE-64L5715o7FlW@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.