linux-nvme.lists.infradead.org archive mirror
 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.17
Date: Tue, 22 Jul 2025 07:04:57 +0100	[thread overview]
Message-ID: <aH8qCeSvpt3eH5g_@infradead.org> (raw)

The following changes since commit ab17ead0e0ee8650cd1cf4e481b1ed0ee9731956:

  block: fix blk_zone_append_update_request_bio() kernel-doc (2025-07-16 10:02:18 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-6.17-2025-07-22

for you to fetch changes up to 5b2c214a95942f7997d1916a4c44017becbc3cac:

  nvme-pci: try function level reset on init failure (2025-07-17 17:46:33 +0200)

----------------------------------------------------------------
nvme updates for Linux 6.17

 - try PCIe function level reset on init failure (Keith Busch)
 - log TLS handshake failures at error level (Maurizio Lombardi)
 - pci-epf: do not complete commands twice if nvmet_req_init() fails
   (Rick Wertenbroek)
 - misc cleanups (Alok Tiwari)

----------------------------------------------------------------
Alok Tiwari (5):
      nvme: fix multiple spelling and grammar issues in host drivers
      nvme: fix incorrect variable in io cqes error message
      nvmet: remove redundant assignment of error code in nvmet_ns_enable()
      nvme: fix typo in status code constant for self-test in progress
      docs: nvme: fix grammar in nvme-pci-endpoint-target.rst

Keith Busch (1):
      nvme-pci: try function level reset on init failure

Maurizio Lombardi (1):
      nvme-tcp: log TLS handshake failures at error level

Rick Wertenbroek (1):
      nvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails

 Documentation/nvme/nvme-pci-endpoint-target.rst | 22 ++++++++++-----------
 drivers/nvme/host/apple.c                       |  4 ++--
 drivers/nvme/host/constants.c                   |  4 ++--
 drivers/nvme/host/core.c                        |  2 +-
 drivers/nvme/host/fc.c                          | 10 +++++-----
 drivers/nvme/host/nvme.h                        |  2 +-
 drivers/nvme/host/pci.c                         | 26 ++++++++++++++++++++++---
 drivers/nvme/host/rdma.c                        |  2 +-
 drivers/nvme/host/tcp.c                         | 11 ++++++++---
 drivers/nvme/target/core.c                      |  2 --
 drivers/nvme/target/passthru.c                  |  4 ++--
 drivers/nvme/target/pci-epf.c                   | 25 ++++++++++++++++--------
 drivers/nvme/target/zns.c                       |  2 +-
 include/linux/nvme.h                            |  2 +-
 14 files changed, 75 insertions(+), 43 deletions(-)


             reply	other threads:[~2025-07-22  6:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22  6:04 Christoph Hellwig [this message]
2025-07-22 10:55 ` [GIT PULL] nvme updates for Linux 6.17 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2025-07-31 14:08 Christoph Hellwig
2025-07-31 16:55 ` 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=aH8qCeSvpt3eH5g_@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;
as well as URLs for NNTP newsgroup(s).