From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH liburing v2] man: document new register/update API
Date: Tue, 31 Aug 2021 13:38:57 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <f456c80bb8795eb7b8c3db8279206d94ce148587.1630436406.git.asml.silence@gmail.com>
On 8/31/21 1:05 PM, Pavel Begunkov wrote:
> Document
> - IORING_REGISTER_FILES2
> - IORING_REGISTER_FILES_UPDATE2,
> - IORING_REGISTER_BUFFERS2
> - IORING_REGISTER_BUFFERS_UPDATE,
>
> And add a couple of words on registered resources (buffers, files)
> tagging.
Great, thanks! I made a few minor edits while applying.
--
Jens Axboe
prev parent reply other threads:[~2021-08-31 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 19:05 [PATCH liburing v2] man: document new register/update API Pavel Begunkov
2021-08-31 19:38 ` Jens Axboe [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 \
[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