Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: hch@lst.de, linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for 7.3
Date: Mon, 5 Oct 2026 08:47:08 -0600	[thread overview]
Message-ID: <cf6376be-e5bb-4c7d-9850-c11b4bbf1e07@kernel.dk> (raw)
In-Reply-To: <asOjta815QimaDcN@kbusch-mbp>

On 10/5/26 7:18 AM, Keith Busch wrote:
> Hi Jens,
> 
> Sending the nvme PR earlier this week as it doesn't look like I'll have
> any other chance for maintenance duties.
> 
> The following changes since commit 684b413b5483f57c890c171b9400076a0143b918:
> 
>   virtio_blk: set the zone write granularity (2026-09-29 12:54:47 -0600)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git tags/nvme-7.3-2026-10-05
> 
> for you to fetch changes up to 5755f1bd0217ffe3c5cf85467bf6b0680f398265:
> 
>   Revert "nvme: do not reset controllers in NVME_CTRL_NEW state" (2026-10-05 06:07:37 -0700)
> 
> ----------------------------------------------------------------
> nvme fixes for Linux 7.3
> 
>  - Fix lock ordering revalidating zoned multipath heads
>  - Fix swapped ZRASF zone state values for full and read only
>  - Fix target p2pmem cleanup when the metadata allocation fails
>  - Fix target status code for invalid NSIDs on reservation features
>  - Revert the NVME_CTRL_NEW state change, which broke the Apple driver

Pulled, thanks.

-- 
Jens Axboe


      reply	other threads:[~2026-10-05 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 13:18 [GIT PULL] nvme fixes for 7.3 Keith Busch
2026-10-05 14:47 ` Jens Axboe [this message]

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=cf6376be-e5bb-4c7d-9850-c11b4bbf1e07@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    /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