public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>,
	linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvmes fixes for Linux 5.19
Date: Thu, 30 Jun 2022 21:45:56 +0200	[thread overview]
Message-ID: <Yr39dC2Hf2/LtgXq@infradead.org> (raw)

The following changes since commit fbb564a557809466c171b95f8d593a0972450ff2:

  lib/sbitmap: Fix invalid loop in __sbitmap_queue_get_batch() (2022-06-25 10:58:55 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-5.19-2022-06-30

for you to fetch changes up to e1c70d79346356bb1ede3f79436df80917845ab9:

  nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1 (2022-06-30 08:24:33 +0200)

----------------------------------------------------------------
nvme fixes for Linux 5.19

 - more quirks (Lamarque Vieira Souza, Pablo Greco)
 - fix a fabrics disconnect regression (Ruozhu Li)
 - fix a nvmet-tcp data_digest calculation regression (Sagi Grimberg)
 - fix nvme-tcp send failure handling (Sagi Grimberg)
 - fix a regression with nvmet-loop and passthrough controllers
   (Alan Adamson)

----------------------------------------------------------------
Alan Adamson (1):
      nvmet: add a clear_ids attribute for passthru targets

Lamarque Vieira Souza (1):
      nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1

Pablo Greco (1):
      nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX S40G)

Ruozhu Li (1):
      nvme: fix regression when disconnect a recovering ctrl

Sagi Grimberg (2):
      nvmet-tcp: fix regression in data_digest calculation
      nvme-tcp: always fail a request when sending it failed

 drivers/nvme/host/core.c       |  2 ++
 drivers/nvme/host/nvme.h       |  1 +
 drivers/nvme/host/pci.c        |  5 +++-
 drivers/nvme/host/rdma.c       | 12 ++++++---
 drivers/nvme/host/tcp.c        | 13 ++++++----
 drivers/nvme/target/configfs.c | 20 +++++++++++++++
 drivers/nvme/target/core.c     |  6 +++++
 drivers/nvme/target/nvmet.h    |  1 +
 drivers/nvme/target/passthru.c | 55 ++++++++++++++++++++++++++++++++++++++++++
 drivers/nvme/target/tcp.c      | 23 +++---------------
 10 files changed, 109 insertions(+), 29 deletions(-)


             reply	other threads:[~2022-06-30 19:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 19:45 Christoph Hellwig [this message]
2022-06-30 20:16 ` [GIT PULL] nvmes fixes for Linux 5.19 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2022-07-07 13:25 Christoph Hellwig
2022-07-07 23:38 ` Jens Axboe
2022-06-23 13:54 Christoph Hellwig
2022-06-23 13:55 ` Jens Axboe
2022-06-23 13:23 Christoph Hellwig
2022-06-23 13:44 ` Jens Axboe
2022-06-23 13:48   ` Christoph Hellwig
2022-06-15 13:37 Christoph Hellwig
2022-06-15 15:39 ` Jens Axboe
2022-06-02  5:28 Christoph Hellwig
2022-06-02  7:49 ` Jens Axboe
2022-06-02  7:59   ` Christoph Hellwig
2022-06-02  8:05     ` 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=Yr39dC2Hf2/LtgXq@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=kbusch@kernel.org \
    --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