From: Keith Busch <kbusch@kernel.org>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: "wagi@monom.org" <wagi@monom.org>, "hch@lst.de" <hch@lst.de>,
"shinichiro.kawasaki@wdc.com" <shinichiro.kawasaki@wdc.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH V2] nvmet: move async event work off nvmet-wq
Date: Mon, 13 Apr 2026 09:24:59 -0600 [thread overview]
Message-ID: <ad0Ky5rrzZt3Xcdu@kbusch-mbp> (raw)
In-Reply-To: <3c93edf3-87fd-486f-bb00-8db2cf925641@nvidia.com>
On Mon, Apr 13, 2026 at 12:11:03AM +0000, Chaitanya Kulkarni wrote:
> Looks like this patch is not merged can you merge this ?
Look again:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=2922e3507f6d5caa7f1d07f145e186fc6f317a4e
next prev parent reply other threads:[~2026-04-13 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 4:30 [PATCH V2] nvmet: move async event work off nvmet-wq Chaitanya Kulkarni
2026-02-26 15:33 ` Christoph Hellwig
2026-03-10 5:44 ` Chaitanya Kulkarni
2026-04-13 0:11 ` Chaitanya Kulkarni
2026-04-13 15:24 ` Keith Busch [this message]
2026-04-13 17:18 ` Chaitanya Kulkarni
2026-03-10 14:23 ` Keith Busch
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=ad0Ky5rrzZt3Xcdu@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.com \
--cc=wagi@monom.org \
/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