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: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me,
	kch@nvidia.com
Subject: Re: [GIT PULL] nvme updates for Linux 6.13
Date: Wed, 13 Nov 2024 10:44:37 -0700	[thread overview]
Message-ID: <104ec93e-b6aa-4c64-93e4-d7a3265b2858@kernel.dk> (raw)
In-Reply-To: <ZzTeMJ60L4mViFPq@kbusch-mbp>

On 11/13/24 10:13 AM, Keith Busch wrote:
> There is an imminent merge conflict with the srcu list fixes (applied to
> upstream 6.12) with the queue freeze lockdep work in block's for-6.13.
> It's a pretty straight forward resolution, but I can send the merge if
> desired.

We already hit that one days ago in linux-next, my for-next branch
already got that one resolved as well. No biggie, simple one.

> nvme updates for Linux 6.13
> 
>  - Use uring_cmd helper (Pavel)
>  - Host Memory Buffer allocation enhancements (Christoph)
>  - Target persistent reservation support (Guixin)
>  - Persistent reservation tracing (Guixen)
>  - NVMe 2.1 specification support (Keith)
>  - Rotational Meta Support (Matias, Wang, Keith)
>  - Volatile cache detection enhancment (Guixen)

Pulled, thanks.

-- 
Jens Axboe



  reply	other threads:[~2024-11-13 17:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13 17:13 [GIT PULL] nvme updates for Linux 6.13 Keith Busch
2024-11-13 17:44 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-21 17:54 Keith Busch
2024-11-21 17:59 ` 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=104ec93e-b6aa-4c64-93e4-d7a3265b2858@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --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