From: Jens Axboe <[email protected]>
To: Dylan Yudaken <[email protected]>, Pavel Begunkov <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH liburing 0/2] tests for deferred multishot completions
Date: Thu, 24 Nov 2022 06:25:09 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 24 Nov 2022 02:30:40 -0800, Dylan Yudaken wrote:
> This adds a couple of tests that expose some trickier corner cases for
> multishot APIS, specifically in light of the latest series to batch &
> defer multishot completion.
>
>
> Dylan Yudaken (2):
> Add a test for errors in multishot recv
> add a test for multishot downgrading
>
> [...]
Applied, thanks!
[1/2] Add a test for errors in multishot recv
(no commit info)
[2/2] add a test for multishot downgrading
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-11-24 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 10:30 [PATCH liburing 0/2] tests for deferred multishot completions Dylan Yudaken
2022-11-24 10:30 ` [PATCH liburing 1/2] Add a test for errors in multishot recv Dylan Yudaken
2022-11-24 10:30 ` [PATCH liburing 2/2] add a test for multishot downgrading Dylan Yudaken
2022-11-24 13:25 ` 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 \
--in-reply-to=166929630942.50735.5964782149427153998.b4-ty@kernel.dk \
[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