From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: hch@lst.de, linux-nvme@lists.infradead.org, sagi@grimberg.me
Subject: Re: [GIT PULL] nvme fixes for Linux 6.12
Date: Thu, 17 Oct 2024 13:12:03 -0600 [thread overview]
Message-ID: <a49bd6e1-c20d-4b88-8c16-a9f00f81129e@kernel.dk> (raw)
In-Reply-To: <ZxFb7BMydvpLbDuh@kbusch-mbp.dhcp.thefacebook.com>
On 10/17/24 12:48 PM, Keith Busch wrote:
> The following changes since commit 8be007c8e0911d0450b402ca8cbb1a8cbd00e8f2:
>
> block: fix blk_rq_map_integrity_sg kernel-doc (2024-09-27 04:19:53 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.12-2024-10-18
>
> for you to fetch changes up to 599d9f3a10eec69ef28a90161763e4bd7c9c02bf:
>
> nvme: use helper nvme_ctrl_state in nvme_keep_alive_finish function (2024-10-17 11:07:37 -0700)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.12
>
> - Fix target passthrough identifier (Nilay)
> - Fix tcp locking (Hannes)
> - Replace list with sbitmap for tracking RDMA rsp tags (Guixen)
> - Remove unnecessary fallthrough statements (Tokunori)
> - Remove ready-without-media support (Greg)
> - Fix multipath partition scan deadlock (Keith)
> - Fix concurrent PCI reset and remove queue mapping (Maurizio)
> - Fabrics shutdown fixes (Nilay)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2024-10-17 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 18:48 [GIT PULL] nvme fixes for Linux 6.12 Keith Busch
2024-10-17 19:12 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-31 15:08 Keith Busch
2024-10-31 15:10 ` 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=a49bd6e1-c20d-4b88-8c16-a9f00f81129e@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.