From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: [PATCH liburing v2 0/5] ranged file slot alloc
Date: Thu, 30 Jun 2022 10:47:12 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 30 Jun 2022 15:10:12 +0100, Pavel Begunkov wrote:
> Add helpers and test ranged file slot allocation feature
>
> Pavel Begunkov (5):
> update io_uring.h with file slot alloc ranges
> alloc range helpers
> file-register: fix return codes
> tests: print file-register errors to stderr
> test range file alloc
>
> [...]
Applied, thanks!
[1/5] update io_uring.h with file slot alloc ranges
commit: 98626db560568fc6f572f829930798f48d226f63
[2/5] alloc range helpers
commit: 161c6a65bd079872fb938665d15802d0e62a9cc9
[3/5] file-register: fix return codes
commit: 52c3bea1ce9926e656b84fb050b61a57f0c3cac8
[4/5] tests: print file-register errors to stderr
commit: c60c80b99f2f425423a7e57a97e359d295b8851c
[5/5] test range file alloc
commit: 5829a98f5f5338502572392de4ac60e0865a44ac
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-06-30 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 14:10 [PATCH liburing v2 0/5] ranged file slot alloc Pavel Begunkov
2022-06-30 14:10 ` [PATCH liburing v2 1/5] update io_uring.h with file slot alloc ranges Pavel Begunkov
2022-06-30 14:10 ` [PATCH liburing v2 2/5] alloc range helpers Pavel Begunkov
2022-06-30 14:10 ` [PATCH liburing v2 3/5] file-register: fix return codes Pavel Begunkov
2022-06-30 14:10 ` [PATCH liburing v2 4/5] tests: print file-register errors to stderr Pavel Begunkov
2022-06-30 14:10 ` [PATCH liburing v2 5/5] test range file alloc Pavel Begunkov
2022-06-30 14:59 ` [PATCH liburing v2 0/5] ranged file slot alloc Jens Axboe
2022-06-30 16:47 ` 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=165660763257.631691.15649768713459002333.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