From: Stefano Garzarella <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected]
Subject: [PATCH liburing 0/3] Add restrictions stuff in the man pages
Date: Fri, 11 Sep 2020 15:34:05 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Jens,
this series adds description of restrictions, how to enable io_uring
ring, and related errors in the man pages.
The patches are also available here:
https://github.com/stefano-garzarella/liburing (branch: restrictions-man-pages)
I didn't put the details of struct io_uring_restriction and
IORING_RESTRICTION_* op codes.
Do you think I should put the definition of the structure and opcodes in
man/io_uring_register.2?
I know I'm not very good at writing documentation, so tell me what to change
or write better ;-)
Thanks,
Stefano
Stefano Garzarella (3):
man/io_uring_setup.2: add IORING_SETUP_R_DISABLED description
man/io_uring_register.2: add description of restrictions
man/io_uring_enter.2: add EACCES and EBADFD errors
man/io_uring_enter.2 | 18 ++++++++++
man/io_uring_register.2 | 79 +++++++++++++++++++++++++++++++++++++++--
man/io_uring_setup.2 | 7 ++++
3 files changed, 102 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-11 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 13:34 Stefano Garzarella [this message]
2020-09-11 13:34 ` [PATCH liburing 1/3] man/io_uring_setup.2: add IORING_SETUP_R_DISABLED description Stefano Garzarella
2020-09-11 13:34 ` [PATCH liburing 2/3] man/io_uring_register.2: add description of restrictions Stefano Garzarella
2020-09-11 15:33 ` Jens Axboe
2020-09-14 8:02 ` Stefano Garzarella
2020-09-11 13:34 ` [PATCH liburing 3/3] man/io_uring_enter.2: add EACCES and EBADFD errors Stefano Garzarella
2020-09-11 15:36 ` Jens Axboe
2020-09-14 8:05 ` Stefano Garzarella
2020-09-14 15:38 ` Jens Axboe
2020-09-14 16:02 ` Stefano Garzarella
2020-09-15 1:35 ` 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 \
[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