From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH liburing 1/1] tests: fixup defer-taskrun.c after api change
Date: Tue, 13 Sep 2022 09:23:43 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <2ed8db2b22f7840977bdc58b6d282be750c878bb.1662900803.git.asml.silence@gmail.com>
On Tue, 13 Sep 2022 13:07:11 +0100, Pavel Begunkov wrote:
>
Applied, thanks!
[1/1] tests: fixup defer-taskrun.c after api change
commit: 2fadaf2ca667fc62f2275e21c229411d0834ec4b
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-09-13 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 12:07 [PATCH liburing 1/1] tests: fixup defer-taskrun.c after api change Pavel Begunkov
2022-09-13 15:23 ` 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=166308262318.27067.7371790942437307726.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