Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.org
Cc: linux-nvme@lists.infradead.org
Subject: [GIT PULL v2] nvme updates for Linux 6.19
Date: Thu, 4 Dec 2025 15:53:35 -0700	[thread overview]
Message-ID: <aTIQ78l7TLpOGPWA@kbusch-mbp> (raw)

Resending due to missing Sign-off-by tags in the previous revision.

The following changes since commit d211a2803551c8ffdf0b97d129388f7d9cc129b5:

  block/rnbd: correct all kernel-doc complaints (2025-12-01 07:19:50 -0700)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-6.19-2025-12-04

for you to fetch changes up to 13989207ee29c40501e719512e8dc90768325895:

  nvme-fabrics: add ENOKEY to no retry criteria for authentication failures (2025-12-04 14:46:17 -0800)

----------------------------------------------------------------
nvme updates for Linux 6.19

 - Subsystem usage cleanups (Max)
 - Endpoint device fixes (Shin'ichiro)
 - Debug statements (Gerd)
 - FC fabrics cleanups and fixes (Daniel)
 - Consistent alloc API usages (Israel)
 - Code comment updates (Chu)
 - Authentication retry fix (Justin)

----------------------------------------------------------------
Chu Guangqing (1):
      nvme: fix typo error in nvme target

Daniel Wagner (5):
      nvme-fc: don't hold rport lock when putting ctrl
      nvme-fc: check all request and response have been processed
      nvmet-fcloop: check all request and response have been processed
      nvmet-fcloop: remove unused lsdir member.
      nvmet-fc: use pr_* print macros instead of dev_*

Gerd Bayer (2):
      nvme-pci: print error message on failure in nvme_probe
      nvme-pci: add debug message on fail to read CSTS

Israel Rukshin (3):
      nvmet-rdma: use kvcalloc for commands and responses arrays
      nvmet-tcp: use kvcalloc for commands array
      nvme-auth: use kvfree() for memory allocated with kvcalloc()

Justin Tee (1):
      nvme-fabrics: add ENOKEY to no retry criteria for authentication failures

Max Gurtovoy (2):
      nvmet: add sanity checks when freeing subsystem
      nvmet: remove redundant subsysnqn field from ctrl

Shin'ichiro Kawasaki (2):
      nvmet: pci-epf: move DMA initialization to EPC init callback
      nvmet: pci-epf: fix DMA channel debug print

 drivers/nvme/host/auth.c        |  2 +-
 drivers/nvme/host/fabrics.c     |  2 +-
 drivers/nvme/host/fc.c          |  8 ++++++--
 drivers/nvme/host/pci.c         |  2 ++
 drivers/nvme/target/admin-cmd.c |  2 +-
 drivers/nvme/target/auth.c      | 18 ++++++++++--------
 drivers/nvme/target/core.c      |  5 +++--
 drivers/nvme/target/fc.c        | 48 +++++++++++++++++++++---------------------------
 drivers/nvme/target/fcloop.c    |  9 ++++++---
 drivers/nvme/target/nvmet.h     |  1 -
 drivers/nvme/target/passthru.c  |  2 +-
 drivers/nvme/target/pci-epf.c   | 14 ++++++++------
 drivers/nvme/target/rdma.c      | 12 ++++++------
 drivers/nvme/target/tcp.c       |  6 +++---
 14 files changed, 69 insertions(+), 62 deletions(-)


             reply	other threads:[~2025-12-04 22:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 22:53 Keith Busch [this message]
2025-12-05  3:25 ` [GIT PULL v2] nvme updates for Linux 6.19 Keith Busch
2025-12-05  4:00   ` 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=aTIQ78l7TLpOGPWA@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    /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