From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH for-next 0/6] clean up __io_fill_cqe_req()
Date: Fri, 17 Jun 2022 07:35:00 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, 17 Jun 2022 09:47:59 +0100, Pavel Begunkov wrote:
> Clean up __io_fill_cqe_req() after recent changes
>
> Pavel Begunkov (6):
> io_uring: don't expose io_fill_cqe_aux()
> io_uring: don't inline __io_get_cqe()
> io_uring: introduce io_req_cqe_overflow()
> io_uring: deduplicate __io_fill_cqe_req tracing
> io_uring: deduplicate io_get_cqe() calls
> io_uring: change ->cqe_cached invariant for CQE32
>
> [...]
Applied, thanks!
[1/6] io_uring: don't expose io_fill_cqe_aux()
(no commit info)
[2/6] io_uring: don't inline __io_get_cqe()
(no commit info)
[3/6] io_uring: introduce io_req_cqe_overflow()
(no commit info)
[4/6] io_uring: deduplicate __io_fill_cqe_req tracing
(no commit info)
[5/6] io_uring: deduplicate io_get_cqe() calls
(no commit info)
[6/6] io_uring: change ->cqe_cached invariant for CQE32
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-17 13:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 8:47 [PATCH for-next 0/6] clean up __io_fill_cqe_req() Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 1/6] io_uring: don't expose io_fill_cqe_aux() Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 2/6] io_uring: don't inline __io_get_cqe() Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 3/6] io_uring: introduce io_req_cqe_overflow() Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 4/6] io_uring: deduplicate __io_fill_cqe_req tracing Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 5/6] io_uring: deduplicate io_get_cqe() calls Pavel Begunkov
2022-06-17 8:48 ` [PATCH for-next 6/6] io_uring: change ->cqe_cached invariant for CQE32 Pavel Begunkov
2022-06-17 13:35 ` 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=165547290061.360864.5731526604877823833.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