Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: [GIT PULL] nvme fixes for Linux 6.10
Date: Wed, 5 Jun 2024 12:10:05 -0600	[thread overview]
Message-ID: <ZmCp_ZJF9ExtjwUP@kbusch-mbp.dhcp.thefacebook.com> (raw)

The following changes since commit 29459c3eaa5c6261fbe0dea7bdeb9b48d35d862a:

  block: Fix zone write plugging handling of devices with a runt zone (2024-05-30 15:03:52 -0600)

are available in the Git repository at:

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

for you to fetch changes up to b1a1fdd7096dd2d67911b07f8118ff113d815db4:

  nvme: fix nvme_pr_* status code parsing (2024-05-31 13:50:59 -0700)

----------------------------------------------------------------
nvme fixes Linux 6.10

 - Use reserved tags for special fabrics operations (Chunguang)
 - Persistent Reservation status masking fix (Weiwen)

----------------------------------------------------------------
Chunguang Xu (1):
      nvme-fabrics: use reserved tag for reg read/write command

Weiwen Hu (1):
      nvme: fix nvme_pr_* status code parsing

 drivers/nvme/host/fabrics.c | 6 +++---
 drivers/nvme/host/pr.c      | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)



             reply	other threads:[~2024-06-05 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 18:10 Keith Busch [this message]
2024-06-05 18:13 ` [GIT PULL] nvme fixes for Linux 6.10 Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2024-06-27 18:03 Keith Busch
2024-06-27 18:15 ` Jens Axboe
2024-05-29 22:10 Keith Busch
2024-05-30  1:55 ` 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=ZmCp_ZJF9ExtjwUP@kbusch-mbp.dhcp.thefacebook.com \
    --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