All of lore.kernel.org
 help / color / mirror / Atom feed
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.12
Date: Wed, 25 Sep 2024 08:40:22 +0200	[thread overview]
Message-ID: <ZvOwViViFuQSeyVk@kbusch-mbp> (raw)

The following changes since commit 65f666c6203600053478ce8e34a1db269a8701c9:

  lib/sbitmap: define swap_lock as raw_spinlock_t (2024-09-20 00:20:06 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-6.12-2024-09-25

for you to fetch changes up to 9064610348b16356d43e59e286aedfec31825541:

  nvme: remove CC register read-back during enabling (2024-09-24 23:35:10 -0700)

----------------------------------------------------------------
nvme fixes for Linux 6.12

 - Multipath fixes (Hannes)
 - Sysfs attribute list NULL terminate fix (Shin'ichiro)
 - Remove problematic read-back (Keith)

----------------------------------------------------------------
Hannes Reinecke (2):
      nvme-multipath: system fails to create generic nvme device
      nvme-multipath: avoid hang on inaccessible namespaces

Keith Busch (1):
      nvme: remove CC register read-back during enabling

Shin'ichiro Kawasaki (1):
      nvme: null terminate nvme_tls_attrs

 drivers/nvme/host/core.c      |  5 -----
 drivers/nvme/host/multipath.c | 14 +++++++++++---
 drivers/nvme/host/sysfs.c     |  1 +
 3 files changed, 12 insertions(+), 8 deletions(-)



             reply	other threads:[~2024-09-25  6:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-25  6:40 Keith Busch [this message]
2024-09-25  9:29 ` [GIT PULL] nvme fixes for Linux 6.12 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2024-10-31 15:08 Keith Busch
2024-10-31 15:10 ` Jens Axboe
2024-10-17 18:48 Keith Busch
2024-10-17 19:12 ` Jens Axboe
2024-09-13 14:34 [GIT PULL] nvme fixes for linux 6.12 Keith Busch
2024-09-13 14:39 ` 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=ZvOwViViFuQSeyVk@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.