public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
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, 5 Jun 2025 11:34:07 +0200	[thread overview]
Message-ID: <aEFkj8jfrDVGuG4_@infradead.org> (raw)

The following changes since commit a2f4c1ae163b815dc81e3cab97c3149fdc6639e3:

  selftests: ublk: kublk: improve behavior on init failure (2025-06-03 20:19:44 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-6.16-2025-06-05

for you to fetch changes up to 44e479d7202070c3bc7f084a4951ee8689769f71:

  nvme: spelling fixes (2025-06-04 10:23:28 +0200)

----------------------------------------------------------------
nvme updates for Linux 6.16

 - TCP error handling fix (Shin'ichiro Kawasaki)
 - TCP I/O stall handling fixes (Hannes Reinecke)
 - fix command limits status code (Keith Busch)
 - support vectored buffers also for passthrough (Pavel Begunkov)
 - spelling fixes (Yi Zhang)

----------------------------------------------------------------
Hannes Reinecke (2):
      nvme-tcp: sanitize request list handling
      nvme-tcp: fix I/O stalls on congested sockets

Keith Busch (1):
      nvme: fix command limits status code

Pavel Begunkov (2):
      nvme: fix implicit bool to flags conversion
      nvme: enable vectored registered bufs for passthrough cmds

Shin'ichiro Kawasaki (1):
      nvme-tcp: remove tag set when second admin queue config fails

Yi Zhang (1):
      nvme: spelling fixes

 drivers/nvme/common/auth.c        |  6 +++---
 drivers/nvme/host/Kconfig         |  2 +-
 drivers/nvme/host/constants.c     |  2 +-
 drivers/nvme/host/core.c          |  3 +--
 drivers/nvme/host/fabrics.c       |  2 +-
 drivers/nvme/host/fabrics.h       |  6 +++---
 drivers/nvme/host/fc.c            |  4 ++--
 drivers/nvme/host/ioctl.c         | 18 ++++++++++--------
 drivers/nvme/host/multipath.c     |  2 +-
 drivers/nvme/host/nvme.h          |  2 +-
 drivers/nvme/host/pci.c           |  4 ++--
 drivers/nvme/host/pr.c            |  2 --
 drivers/nvme/host/rdma.c          |  4 ++--
 drivers/nvme/host/tcp.c           | 24 +++++++++++++++++++++---
 drivers/nvme/target/admin-cmd.c   |  2 +-
 drivers/nvme/target/core.c        | 11 ++---------
 drivers/nvme/target/fc.c          |  2 +-
 drivers/nvme/target/io-cmd-bdev.c | 11 ++---------
 drivers/nvme/target/passthru.c    |  2 +-
 include/linux/nvme.h              |  2 +-
 20 files changed, 57 insertions(+), 54 deletions(-)

             reply	other threads:[~2025-06-05  9:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-05  9:34 Christoph Hellwig [this message]
2025-06-05 13:42 ` [GIT PULL] nvme updates for Linux 6.16 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2025-06-26 11:07 Christoph Hellwig
2025-06-26 12:09 ` Keith Busch
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=aEFkj8jfrDVGuG4_@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