From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: hch@lst.de, linux-nvme@lists.infradead.org, joshi.k@samsung.com,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] nvme-pci: fix missed admin queue sq doorbell write
Date: Wed, 22 Apr 2026 08:01:55 +0200 [thread overview]
Message-ID: <20260422060155.GA5391@lst.de> (raw)
In-Reply-To: <20260421161855.3980034-1-kbusch@meta.com>
On Tue, Apr 21, 2026 at 09:18:55AM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> We can batch admin commands, which means bd->last may be false,
How do we end up batching them? io_uring passthrough I guess? Can
you expand the commit log a bit with that?
Otherwise looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-04-22 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260421162015epcas5p3ba67958507806dd09025a2a85b3ddf89@epcas5p3.samsung.com>
2026-04-21 16:18 ` [PATCH] nvme-pci: fix missed admin queue sq doorbell write Keith Busch
2026-04-22 6:01 ` Christoph Hellwig [this message]
2026-04-22 9:43 ` Kanchan Joshi
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=20260422060155.GA5391@lst.de \
--to=hch@lst.de \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-nvme@lists.infradead.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