From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: linux-block@vger.kernel.org, io-uring@vger.kernel.org,
linux-nvme@lists.infradead.org, hch@lst.de, axboe@kernel.dk,
sagi@grimberg.me, joshi.k@samsung.com,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv3 2/2] nvme: improved uring polling
Date: Tue, 13 Jun 2023 06:30:38 +0200 [thread overview]
Message-ID: <20230613043038.GA13343@lst.de> (raw)
In-Reply-To: <20230612190343.2087040-3-kbusch@meta.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2023-06-13 4:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 19:03 [PATCHv3 0/2] enhanced nvme uring command polling Keith Busch
2023-06-12 19:03 ` [PATCHv3 1/2] block: add request polling helper Keith Busch
2023-06-12 19:03 ` [PATCHv3 2/2] nvme: improved uring polling Keith Busch
2023-06-13 4:30 ` Christoph Hellwig [this message]
2023-06-13 7:56 ` Sagi Grimberg
2023-06-28 22:13 ` [PATCHv3 0/2] enhanced nvme uring command polling 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=20230613043038.GA13343@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.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