linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: sagi@grimberg.me, hch@lst.de, linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme updates for Linux 6.10
Date: Tue, 14 May 2024 09:07:44 -0600	[thread overview]
Message-ID: <ZkN-QMZ9qE47zhFk@kbusch-mbp> (raw)

The following changes since commit 6ad0d7e0f4b68f87a98ea2b239123b7d865df86b:

  sbitmap: use READ_ONCE to access map->word (2024-04-26 07:40:28 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-6.10-2024-05-14

for you to fetch changes up to 54a76c8732b265aa86030134d4af6a5a3c59fe52:

  nvme-rdma, nvme-tcp: include max reconnects for reconnect logging (2024-05-07 08:50:37 -0700)

----------------------------------------------------------------
nvme updates for Linux 6.10

 - Fabrics connection retries (Daniel, Hannes)
 - Fabrics logging enhancements (Tokunori)
 - RDMA delete optimization (Sagi)

----------------------------------------------------------------
Daniel Wagner (1):
      nvme: do not retry authentication failures

Hannes Reinecke (4):
      nvmet: lock config semaphore when accessing DH-HMAC-CHAP key
      nvmet: return DHCHAP status codes from nvmet_setup_auth()
      nvme: return kernel error codes for admin queue connect
      nvme-fabrics: short-circuit reconnect retries

Sagi Grimberg (1):
      nvmet-rdma: Avoid o(n^2) loop in delete_ctrl

Tokunori Ikegami (1):
      nvme-rdma, nvme-tcp: include max reconnects for reconnect logging

 drivers/nvme/host/auth.c               |  6 +++---
 drivers/nvme/host/core.c               |  6 +++---
 drivers/nvme/host/fabrics.c            | 51 ++++++++++++++++++++++++++++++++-------------------
 drivers/nvme/host/fabrics.h            |  2 +-
 drivers/nvme/host/fc.c                 |  4 +---
 drivers/nvme/host/nvme.h               |  2 +-
 drivers/nvme/host/rdma.c               | 23 ++++++++++++++---------
 drivers/nvme/host/tcp.c                | 30 ++++++++++++++++++------------
 drivers/nvme/target/auth.c             | 22 ++++++++++------------
 drivers/nvme/target/configfs.c         | 22 +++++++++++++++++-----
 drivers/nvme/target/fabrics-cmd-auth.c | 49 +++++++++++++++++++++++++------------------------
 drivers/nvme/target/fabrics-cmd.c      | 11 ++++++-----
 drivers/nvme/target/nvmet.h            |  8 ++++----
 drivers/nvme/target/rdma.c             | 16 ++++++----------
 14 files changed, 141 insertions(+), 111 deletions(-)


             reply	other threads:[~2024-05-14 15:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 15:07 Keith Busch [this message]
2024-05-14 15:30 ` [GIT PULL] nvme updates for Linux 6.10 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=ZkN-QMZ9qE47zhFk@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 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).