Linux-NVME Archive on lore.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 fixes for Linux 6.15
Date: Thu, 15 May 2025 13:56:05 +0200	[thread overview]
Message-ID: <aCXWVQ0-cbSsQXFk@infradead.org> (raw)

The following changes since commit 8098514bd5ca98beca6ec725751d82d0d5b492d8:

  block: always allocate integrity buffer when required (2025-05-12 07:14:03 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-6.15-2025-05-15

for you to fetch changes up to e765bf89f42b5c82132a556b630affeb82b2a21f:

  nvme-pci: add NVME_QUIRK_NO_DEEPEST_PS quirk for SOLIDIGM P44 Pro (2025-05-14 17:16:16 +0200)

----------------------------------------------------------------
nvme fixes for linux 6.15

 - fixes for atomic writes (Alan Adamson)
 - fixes for polled CQs in nvmet-epf (Damien Le Moal)
 - fix for polled CQs in nvme-pci (Keith Busch)
 - fix compile on odd configs that need to be forced to inline
   (Kees Cook)
 - one more quirk (Ilya Guterman)

----------------------------------------------------------------
Alan Adamson (2):
      nvme: multipath: enable BLK_FEAT_ATOMIC_WRITES for multipathing
      nvme: all namespaces in a subsystem must adhere to a common atomic write size

Damien Le Moal (5):
      nvmet: pci-epf: clear completion queue IRQ flag on delete
      nvmet: pci-epf: do not fall back to using INTX if not supported
      nvmet: pci-epf: cleanup nvmet_pci_epf_raise_irq()
      nvmet: pci-epf: improve debug message
      nvmet: pci-epf: remove NVMET_PCI_EPF_Q_IS_SQ

Ilya Guterman (1):
      nvme-pci: add NVME_QUIRK_NO_DEEPEST_PS quirk for SOLIDIGM P44 Pro

Kees Cook (1):
      nvme-pci: make nvme_pci_npages_prp() __always_inline

Keith Busch (1):
      nvme-pci: acquire cq_poll_lock in nvme_poll_irqdisable

 drivers/nvme/host/core.c      | 30 +++++++++++++++++++++++++++---
 drivers/nvme/host/multipath.c |  3 ++-
 drivers/nvme/host/nvme.h      |  3 ++-
 drivers/nvme/host/pci.c       |  6 +++++-
 drivers/nvme/target/pci-epf.c | 39 +++++++++++++++++++++++----------------
 5 files changed, 59 insertions(+), 22 deletions(-)


             reply	other threads:[~2025-05-15 11:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 11:56 Christoph Hellwig [this message]
2025-05-15 12:21 ` [GIT PULL] nvme fixes for Linux 6.15 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2025-05-08 15:07 Christoph Hellwig
2025-05-08 15:14 ` Jens Axboe
2025-05-01 13:33 Christoph Hellwig
2025-05-01 13:56 ` Jens Axboe
2025-04-24 11:23 hch
2025-04-24 12:28 ` Jens Axboe
2025-04-17  6:47 Christoph Hellwig
2025-04-17 12:19 ` 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=aCXWVQ0-cbSsQXFk@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