From: "Drew DeVault" <[email protected]>
To: "Jens Axboe" <[email protected]>, <[email protected]>
Cc: "Pavel Begunkov" <[email protected]>
Subject: Re: [PATCH] io_uring_enter(2): clarify OP_READ and OP_WRITE
Date: Sun, 23 May 2021 12:44:31 -0400 [thread overview]
Message-ID: <CBKRYME7X23G.1ECMG1DI27KNE@taiga> (raw)
In-Reply-To: <[email protected]>
On Sun May 23, 2021 at 12:41 PM EDT, Jens Axboe wrote:
> They do, if -1 is used as the offset. Care to update the patch and
> include that clarification?
Certainly.
prev parent reply other threads:[~2021-05-23 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 16:20 [PATCH] io_uring_enter(2): clarify OP_READ and OP_WRITE Drew DeVault
2021-05-23 16:41 ` Jens Axboe
2021-05-23 16:44 ` Drew DeVault [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=CBKRYME7X23G.1ECMG1DI27KNE@taiga \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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