From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 7/7] io_submit01: Add docparse formatting and more detailed description
Date: Mon, 21 Jun 2021 15:17:07 +0200 [thread overview]
Message-ID: <YNCRU7dN7puCLcSp@yuki> (raw)
In-Reply-To: <20210618094210.183027-8-xieziyao@huawei.com>
Hi!
> + * 1. io_submit fails and returns -EINVAL if ctx is invalid.
> + * 2. io_submit fails and returns -EINVAL if nr is invalid.
> + * 3. io_submit fails and returns -EFAULT if iocbpp pointer is invalid.
> + * 4. io_submit fails and returns -EBADF if fd is invalid.
> + * 5. io_submit() succeeds and returns the number of iocbs submitted.
> + * 6. io_submit() succeeds and returns 0 if nr is zero.
Did the same change here and pushed as well, thanks.
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2021-06-21 13:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 9:42 [LTP] [PATCH 0/7] syscalls/aio: Add tests for libaio and docparse formatting Xie Ziyao
2021-06-18 9:42 ` [LTP] [PATCH 1/7] io_cancel02: Add io_cancel02 test for libaio Xie Ziyao
2021-06-21 8:42 ` Cyril Hrubis
2021-06-21 9:01 ` Cyril Hrubis
2021-06-18 9:42 ` [LTP] [PATCH 2/7] io_cancel01: Add .needs_kconfigs and more detailed description Xie Ziyao
2021-06-21 8:46 ` Cyril Hrubis
2021-06-18 9:42 ` [LTP] [PATCH 3/7] io_destroy01: Add docparse formatting " Xie Ziyao
2021-06-21 8:52 ` Cyril Hrubis
2021-06-18 9:42 ` [LTP] [PATCH 4/7] io_getevents01: Add .needs_kconfigs " Xie Ziyao
2021-06-21 8:55 ` Cyril Hrubis
2021-06-18 9:42 ` [LTP] [PATCH 5/7] io_getevents02: Add io_getevents02 test for libaio Xie Ziyao
2021-06-21 9:02 ` Cyril Hrubis
2021-06-22 9:18 ` Xie Ziyao
2021-06-18 9:42 ` [LTP] [PATCH 6/7] io_setup: Add docparse formatting and more detailed description Xie Ziyao
2021-06-21 12:58 ` Cyril Hrubis
2021-06-18 9:42 ` [LTP] [PATCH 7/7] io_submit01: " Xie Ziyao
2021-06-21 13:17 ` Cyril Hrubis [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=YNCRU7dN7puCLcSp@yuki \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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