From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH next 0/5] simplify SCM accounting
Date: Thu, 07 Apr 2022 11:55:06 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 7 Apr 2022 13:40:00 +0100, Pavel Begunkov wrote:
> Just a refactoring series killing some lines of the SCM registration
> side and making it simpler overall.
>
> Pavel Begunkov (5):
> io_uring: uniform SCM accounting
> io_uring: refactor __io_sqe_files_scm
> io_uring: don't pass around fixed index for scm
> io_uring: deduplicate SCM accounting
> io_uring: rename io_sqe_file_register
>
> [...]
Applied, thanks!
[1/5] io_uring: uniform SCM accounting
commit: b302191999697ac6972c70d38d16a8a3e9546216
[2/5] io_uring: refactor __io_sqe_files_scm
commit: daee35f002ecabfaf6b9c6d5adc727b40aeaa048
[3/5] io_uring: don't pass around fixed index for scm
commit: 6c5f2c03659346f28334b3c757c8e752d96c41e2
[4/5] io_uring: deduplicate SCM accounting
commit: f8b9357ae7788235abc84ffc8fe1c66e8607aa47
[5/5] io_uring: rename io_sqe_file_register
commit: d9ed9fcf4bd6b8997d7e7533b650e18fa6273ed1
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-04-07 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 12:40 [PATCH next 0/5] simplify SCM accounting Pavel Begunkov
2022-04-07 12:40 ` [PATCH 1/5] io_uring: uniform " Pavel Begunkov
2022-04-07 12:40 ` [PATCH 2/5] io_uring: refactor __io_sqe_files_scm Pavel Begunkov
2022-04-07 12:40 ` [PATCH 3/5] io_uring: don't pass around fixed index for scm Pavel Begunkov
2022-04-07 12:40 ` [PATCH 4/5] io_uring: deduplicate SCM accounting Pavel Begunkov
2022-04-07 12:40 ` [PATCH 5/5] io_uring: rename io_sqe_file_register Pavel Begunkov
2022-04-07 17:54 ` [PATCH next 0/5] simplify SCM accounting Jens Axboe
2022-04-07 17:55 ` 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=164935410648.218477.4736604874036916352.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