From: Jens Axboe <[email protected]>
To: Dylan Yudaken <[email protected]>, Pavel Begunkov <[email protected]>
Cc: [email protected], [email protected]
Subject: Re: [PATCH liburing] Do not always expect multishot recv to stop posting events
Date: Mon, 07 Nov 2022 13:18:10 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 7 Nov 2022 05:04:04 -0800, Dylan Yudaken wrote:
> Later kernels can have a fix that does not stop multishot from posting
> events, and would just continue in overflow mode.
>
>
Applied, thanks!
[1/1] Do not always expect multishot recv to stop posting events
commit: 0d4fdb416718a70a4a90c5c4722b38cf44849195
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-11-07 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 13:04 [PATCH liburing] Do not always expect multishot recv to stop posting events Dylan Yudaken
2022-11-07 20:18 ` 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=166785229052.23588.9277094867339486082.b4-ty@kernel.dk \
[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