public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [GIT PULL] nvme fixes for Linux 7.0
Date: Wed, 4 Mar 2026 08:16:07 -0700	[thread overview]
Message-ID: <c8f1f6cb-efa4-4422-b697-949e15004861@kernel.dk> (raw)
In-Reply-To: <aahLbUJOav9p1mfx@kbusch-mbp>

On 3/4/26 8:10 AM, Keith Busch wrote:
> The following changes since commit 91e1c1bcf0f2376f40ac859cf17d0a64a605e662:
> 
>   block, nvme: remove unused dma_iova_state function parameter (2026-01-13 07:23:39 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git tags/nvme-7.0-2026-03-04
> 
> for you to fetch changes up to c3320153769f05fd7fe9d840cb555dd3080ae424:
> 
>   nvme: fix memory allocation in nvme_pr_read_keys() (2026-03-04 06:53:41 -0800)
> 
> ----------------------------------------------------------------
> nvme fixes for Linux 7.0
> 
>  - Improve quirk visibility and configurability (Maurizio)
>  - Fix runtime user modification to queue setup (Keith)
>  - Fix multipath leak on try_module_get failure (Keith)
>  - Ignore ambiguous spec definitions for better atomics support (John)
>  - Fix admin queue leak on controller reset (Ming)
>  - Fix large allocation in persistent reservation read keys (Sungwoo Kim)
>  - Fix fcloop callback handling (Justin)
>  - Securely free DHCHAP secrets (Daniel)
>  - Various cleanups and typo fixes (John, Wilfred)

Pulled, thanks.

-- 
Jens Axboe



  reply	other threads:[~2026-03-04 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 15:10 [GIT PULL] nvme fixes for Linux 7.0 Keith Busch
2026-03-04 15:16 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-12 21:07 Keith Busch
2026-03-12 21:16 ` 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=c8f1f6cb-efa4-4422-b697-949e15004861@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@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