From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-block@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for Linux 6.15
Date: Thu, 15 May 2025 06:21:27 -0600 [thread overview]
Message-ID: <b81d2ab9-0ebb-4498-a136-9a65eecfc6a1@kernel.dk> (raw)
In-Reply-To: <aCXWVQ0-cbSsQXFk@infradead.org>
On 5/15/25 5:56 AM, Christoph Hellwig wrote:
> The following changes since commit 8098514bd5ca98beca6ec725751d82d0d5b492d8:
>
> block: always allocate integrity buffer when required (2025-05-12 07:14:03 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.15-2025-05-15
>
> for you to fetch changes up to e765bf89f42b5c82132a556b630affeb82b2a21f:
>
> nvme-pci: add NVME_QUIRK_NO_DEEPEST_PS quirk for SOLIDIGM P44 Pro (2025-05-14 17:16:16 +0200)
>
> ----------------------------------------------------------------
> nvme fixes for linux 6.15
>
> - fixes for atomic writes (Alan Adamson)
> - fixes for polled CQs in nvmet-epf (Damien Le Moal)
> - fix for polled CQs in nvme-pci (Keith Busch)
> - fix compile on odd configs that need to be forced to inline
> (Kees Cook)
> - one more quirk (Ilya Guterman)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2025-05-15 12:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 11:56 [GIT PULL] nvme fixes for Linux 6.15 Christoph Hellwig
2025-05-15 12:21 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-08 15:07 Christoph Hellwig
2025-05-08 15:14 ` Jens Axboe
2025-05-01 13:33 Christoph Hellwig
2025-05-01 13:56 ` Jens Axboe
2025-04-24 11:23 hch
2025-04-24 12:28 ` Jens Axboe
2025-04-17 6:47 Christoph Hellwig
2025-04-17 12:19 ` 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=b81d2ab9-0ebb-4498-a136-9a65eecfc6a1@kernel.dk \
--to=axboe@kernel.dk \
--cc=axboe@fb.com \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox