From: Jens Axboe <axboe@kernel.dk>
To: 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, 24 Apr 2025 06:28:16 -0600 [thread overview]
Message-ID: <faf4ed42-1842-469b-b052-c88a8324ef3b@kernel.dk> (raw)
In-Reply-To: <aAofJOcb2NzkXsP9@infradead.org>
On 4/24/25 5:23 AM, hch@infradead.org wrote:
> The following changes since commit 81dd1feb19c7a812e51fa6e2f988f4def5e6ae39:
>
> Merge tag 'nvme-6.15-2025-04-17' of git://git.infradead.org/nvme into block-6.15 (2025-04-17 06:18:49 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.15-2025-04-24
>
> for you to fetch changes up to 3d7aa0c7b4e96cd460826d932e44710cdeb3378b:
>
> nvmet: fix out-of-bounds access in nvmet_enable_port (2025-04-22 09:50:28 +0200)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.15
>
> - fix an out-of-bounds access in nvmet_enable_port (Richard Weinberger)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2025-04-24 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 11:23 [GIT PULL] nvme fixes for Linux 6.15 hch
2025-04-24 12:28 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-15 11:56 Christoph Hellwig
2025-05-15 12:21 ` Jens Axboe
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-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=faf4ed42-1842-469b-b052-c88a8324ef3b@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