From: Gabriel Krisman Bertazi <[email protected]>
To: Pavel Begunkov <[email protected]>
Cc: [email protected], Jens Axboe <[email protected]>
Subject: Re: [PATCH for-next 1/1] io_uring: inline __io_req_complete_post()
Date: Thu, 17 Nov 2022 14:49:33 -0500 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <ef4c9059950a3da5cf68df00f977f1fd13bd9306.1668597569.git.asml.silence@gmail.com> (Pavel Begunkov's message of "Thu, 17 Nov 2022 18:41:06 +0000")
Pavel Begunkov <[email protected]> writes:
> There is only one user of __io_req_complete_post(), inline it.
Probably already inlined by the compiler, so shouldn't be a problem.
Feel free to add:
Reviewed-by: Gabriel Krisman Bertazi <[email protected]>
Thanks,
--
Gabriel Krisman Bertazi
prev parent reply other threads:[~2022-11-17 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 18:41 [PATCH for-next 1/1] io_uring: inline __io_req_complete_post() Pavel Begunkov
2022-11-17 19:46 ` Jens Axboe
2022-11-17 19:49 ` Gabriel Krisman Bertazi [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 \
[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