All of lore.kernel.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] nvme fixes for Linux 6.0
Date: Thu, 11 Aug 2022 16:05:25 +0200	[thread overview]
Message-ID: <YvUMpS5PxgJSykCB@infradead.org> (raw)

The following changes since commit fa9db655d0e112c108fe838809608caf759bdf5e:

  Merge tag 'for-5.20/block-2022-08-04' of git://git.kernel.dk/linux-block (2022-08-04 20:00:14 -0700)

are available in the Git repository at:

  git://git.infradead.org/nvme.git tags/nvme-6.0-2022-08-11

for you to fetch changes up to f37527a09dac324c74bb341c841096395a2f2566:

  nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG GAMMIX S70 (2022-08-11 14:10:16 +0200)

----------------------------------------------------------------
nvme fixes for Linux 6.0

 - print nvme connect Linux error codes properly (Amit Engel)
 - fix the fc_appid_store return value (Christoph Hellwig)
 - fix a typo in an error message (Christophe JAILLET)
 - add another non-unique identifier quirk (Dennis P. Kliem)
 - check if the queue is allocated before stopping it in nvme-tcp
   (Maurizio Lombardi)
 - restart admin queue if the caller needs to restart queue in nvme-fc
   (Ming Lei)
 - use kmemdup instead of kmalloc + memcpy in nvme-auth (Zhang Xiaoxu)

----------------------------------------------------------------
Amit Engel (1):
      nvme-fabrics: parse nvme connect Linux error codes

Christoph Hellwig (1):
      nvme-fc: fix the fc_appid_store return value

Christophe JAILLET (1):
      nvme-fabrics: Fix a typo in an error message

Dennis P. Kliem (1):
      nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG GAMMIX S70

Maurizio Lombardi (1):
      nvme-tcp: check if the queue is allocated before stopping it

Ming Lei (1):
      nvme-fc: restart admin queue if the caller needs to restart queue

Zhang Xiaoxu (1):
      nvmet-auth: use kmemdup instead of kmalloc + memcpy

 drivers/nvme/host/fabrics.c            | 8 +++++++-
 drivers/nvme/host/fc.c                 | 5 ++++-
 drivers/nvme/host/pci.c                | 2 ++
 drivers/nvme/host/tcp.c                | 3 +++
 drivers/nvme/target/fabrics-cmd-auth.c | 4 ++--
 5 files changed, 18 insertions(+), 4 deletions(-)

             reply	other threads:[~2022-08-11 14:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 14:05 Christoph Hellwig [this message]
2022-08-11 14:38 ` [GIT PULL] nvme fixes for Linux 6.0 Jens Axboe
2022-09-01  7:29 Christoph Hellwig
2022-09-01 14:11 ` Jens Axboe
2022-09-08 15:35 Christoph Hellwig
2022-09-08 16:20 ` Jens Axboe
2022-09-29 15:02 Christoph Hellwig
2022-09-29 15: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=YvUMpS5PxgJSykCB@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 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.