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 6.12
Date: Thu, 31 Oct 2024 09:10:29 -0600 [thread overview]
Message-ID: <6ff663d8-cb7d-493d-9890-d09aa5f4a491@kernel.dk> (raw)
In-Reply-To: <ZyOdZWK7S1Q-VbcK@kbusch-mbp.dhcp.thefacebook.com>
On 10/31/24 9:08 AM, Keith Busch wrote:
> The following changes since commit 49c234b50a437eb827832b61cd662e9aa382f31a:
>
> Merge tag 'md-6.12-20241018' of https://git.kernel.org/pub/scm/linux/kernel/git/song/md into block-6.12 (2024-10-18 10:58:24 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.12-2024-10-31
>
> for you to fetch changes up to 5eed4fb274cd6579f2fb4190b11c4c86c553cd06:
>
> nvme: re-fix error-handling for io_uring nvme-passthrough (2024-10-30 07:19:18 -0700)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.12
>
> - Spec compliant identification fix (Keith)
> - Module parameter to enable backward compatibility on unusual
> namespace formats (Keith)
> - Target double free fix when using keys (Vitaliy)
> - Passthrough command error handling fix (Keith)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2024-10-31 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 15:08 [GIT PULL] nvme fixes for Linux 6.12 Keith Busch
2024-10-31 15:10 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-17 18:48 Keith Busch
2024-10-17 19:12 ` Jens Axboe
2024-09-25 6:40 Keith Busch
2024-09-25 9:29 ` Jens Axboe
2024-09-13 14:34 [GIT PULL] nvme fixes for linux 6.12 Keith Busch
2024-09-13 14:39 ` 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=6ff663d8-cb7d-493d-9890-d09aa5f4a491@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.