From: Pavel Begunkov <asml.silence@gmail.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
"io-uring@vger.kernel.org" <io-uring@vger.kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Kanchan Joshi <joshi.k@samsung.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH for-next] nvme: use helpers to access io_uring cmd space
Date: Mon, 21 Oct 2024 17:04:00 +0100 [thread overview]
Message-ID: <106bc650-a79f-4408-b096-76d49a495195@gmail.com> (raw)
In-Reply-To: <b82b36c3-5ab5-4e99-941b-b099020d1b36@nvidia.com>
On 10/19/24 01:44, Chaitanya Kulkarni wrote:
> + (linux-nvme)
My bad, lost CC nvme. Thanks for review
> On 10/18/24 09:16, Pavel Begunkov wrote:
>> Command implementations shouldn't be directly looking into io_uring_cmd
>> to carve free space. Use an io_uring helper, which will also do build
>> time size sanitisation.
>>
>> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
--
Pavel Begunkov
prev parent reply other threads:[~2024-10-21 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c274d35f441c649f0b725c70f681ec63774fce3b.1729265044.git.asml.silence@gmail.com>
2024-10-19 0:44 ` [PATCH for-next] nvme: use helpers to access io_uring cmd space Chaitanya Kulkarni
2024-10-21 16:04 ` Pavel Begunkov [this message]
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=106bc650-a79f-4408-b096-76d49a495195@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=chaitanyak@nvidia.com \
--cc=io-uring@vger.kernel.org \
--cc=joshi.k@samsung.com \
--cc=linux-block@vger.kernel.org \
--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