From: Dylan Yudaken <[email protected]>
To: "[email protected]" <[email protected]>
Cc: Kernel Team <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [PATCH v2 liburing 5/7] add recv-multishot test
Date: Thu, 30 Jun 2022 16:53:13 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAFBCWQJqVZNQw8rxU1LihhVj5jkfTPqhHbHiPjh=Z6WiF+vODg@mail.gmail.com>
On Thu, 2022-06-30 at 18:24 +0700, Ammar Faizi wrote:
> Dylan,
>
> On Thu, Jun 30, 2022 at 4:19 PM Dylan Yudaken wrote:
> > add a test for multishot receive functionality
> >
> > Signed-off-by: Dylan Yudaken <[email protected]>
>
> Since commit 68103b731c34a9f83c181cb33eb424f46f3dcb94 ("Merge branch
> 'exitcode-protocol' of ...."), we have a new rule for exit code.
>
> The exit code protocol we have here is:
> - Use T_EXIT_SKIP when you skip the test.
> - Use T_EXIT_PASS when the test passes.
> - Use T_EXIT_FAIL when the test fails.
>
Ah I did not notice this new stuff.
Fixed this (and the other comment) in v3.
Thanks!
next prev parent reply other threads:[~2022-06-30 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 9:14 [PATCH v2 liburing 0/7] liburing: multishot receive Dylan Yudaken
2022-06-30 9:14 ` [PATCH v2 liburing 1/7] add t_create_socket_pair Dylan Yudaken
2022-06-30 11:31 ` Ammar Faizi
2022-06-30 9:14 ` [PATCH v2 liburing 2/7] add IORING_RECV_MULTISHOT to io_uring.h Dylan Yudaken
2022-06-30 9:14 ` [PATCH v2 liburing 3/7] add io_uring_prep_(recv|recvmsg)_multishot Dylan Yudaken
2022-06-30 9:14 ` [PATCH v2 liburing 4/7] add IORING_RECV_MULTISHOT docs Dylan Yudaken
2022-06-30 9:14 ` [PATCH v2 liburing 5/7] add recv-multishot test Dylan Yudaken
2022-06-30 11:24 ` Ammar Faizi
2022-06-30 16:53 ` Dylan Yudaken [this message]
2022-06-30 9:14 ` [PATCH v2 liburing 6/7] add poll overflow test Dylan Yudaken
2022-06-30 9:14 ` [PATCH v2 liburing 7/7] add accept with " Dylan Yudaken
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=6111225a7715d466782755cdb67f0cf4fc5e97b5.camel@fb.com \
[email protected] \
[email protected] \
[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