From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH 5.19 0/6] CQE32 fixes
Date: Wed, 15 Jun 2022 15:23:56 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Wed, 15 Jun 2022 11:23:01 +0100, Pavel Begunkov wrote:
> Several fixes for IORING_SETUP_CQE32
>
> Pavel Begunkov (6):
> io_uring: get rid of __io_fill_cqe{32}_req()
> io_uring: unite fill_cqe and the 32B version
> io_uring: fill extra big cqe fields from req
> io_uring: fix ->extra{1,2} misuse
> io_uring: inline __io_fill_cqe()
> io_uring: make io_fill_cqe_aux to honour CQE32
>
> [...]
Applied, thanks!
[1/6] io_uring: get rid of __io_fill_cqe{32}_req()
(no commit info)
[2/6] io_uring: unite fill_cqe and the 32B version
(no commit info)
[3/6] io_uring: fill extra big cqe fields from req
(no commit info)
[4/6] io_uring: fix ->extra{1,2} misuse
(no commit info)
[5/6] io_uring: inline __io_fill_cqe()
(no commit info)
[6/6] io_uring: make io_fill_cqe_aux to honour CQE32
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-15 21:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 10:23 [PATCH 5.19 0/6] CQE32 fixes Pavel Begunkov
2022-06-15 10:23 ` [PATCH 5.19 1/6] io_uring: get rid of __io_fill_cqe{32}_req() Pavel Begunkov
2022-06-15 10:23 ` [PATCH 5.19 2/6] io_uring: unite fill_cqe and the 32B version Pavel Begunkov
2022-06-15 10:23 ` [PATCH 5.19 3/6] io_uring: fill extra big cqe fields from req Pavel Begunkov
2022-06-15 10:23 ` [PATCH 5.19 4/6] io_uring: fix ->extra{1,2} misuse Pavel Begunkov
2022-06-15 10:23 ` [PATCH 5.19 5/6] io_uring: inline __io_fill_cqe() Pavel Begunkov
2022-06-15 10:23 ` [PATCH 5.19 6/6] io_uring: make io_fill_cqe_aux to honour CQE32 Pavel Begunkov
2022-06-15 12:03 ` [PATCH 5.19 0/6] CQE32 fixes Jens Axboe
2022-06-15 12:21 ` Pavel Begunkov
2022-06-15 12:24 ` Jens Axboe
2022-06-15 21: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=165532823636.852896.7626951550140433327.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