From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH 0/2] improve multishot error codes
Date: Mon, 10 Mar 2025 07:14:50 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Sat, 08 Mar 2025 17:19:31 +0000, Pavel Begunkov wrote:
> Unify error codes between normal execution path and multishot. It's
> a dependency for other work, but it should stand well as independent
> cleanups.
>
> Pavel Begunkov (2):
> io_uring: return -EAGAIN to continue multishot
> io_uring: unify STOP_MULTISHOT with IOU_OK
>
> [...]
Applied, thanks!
[1/2] io_uring: return -EAGAIN to continue multishot
commit: 7a9dcb05f5501b07a2ef7d0ef743f4f17e9f3055
[2/2] io_uring: unify STOP_MULTISHOT with IOU_OK
commit: 5027d02452c982bdc7b36205c66466ebd7e6ee17
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-03-10 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-08 17:19 [PATCH 0/2] improve multishot error codes Pavel Begunkov
2025-03-08 17:19 ` [PATCH 1/2] io_uring: return -EAGAIN to continue multishot Pavel Begunkov
2025-03-08 17:19 ` [PATCH 2/2] io_uring: unify STOP_MULTISHOT with IOU_OK Pavel Begunkov
2025-03-10 13:14 ` 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=174161249059.148284.11393421808958696583.b4-ty@kernel.dk \
[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