From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH liburing 0/4] test kernel allocated regions
Date: Mon, 09 Dec 2024 14:16:03 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Wed, 20 Nov 2024 23:39:47 +0000, Pavel Begunkov wrote:
> Patch 1 excersices one additional failure path for user provided regions,
> and the rest test kernel allocated regions.
>
> Pavel Begunkov (4):
> tests/reg-wait: test registering RO memory
> test/reg-wait: basic test + probing of kernel regions
> test/reg-wait: add allocation abstraction
> test/reg-wait: test kernel allocated regions
>
> [...]
Applied, thanks!
[1/4] tests/reg-wait: test registering RO memory
commit: 67a8f570f9e14aef41c880d60edb675f4517f267
[2/4] test/reg-wait: basic test + probing of kernel regions
commit: 30ce99006af9403ffdb84ea31223fb0c13f7612e
[3/4] test/reg-wait: add allocation abstraction
commit: b526f2354b49acc120ff9abd9cd245ef62f07325
[4/4] test/reg-wait: test kernel allocated regions
commit: 895b45b59e10b543f5c0b9d901d9f39da7687c07
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-12-09 21:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 23:39 [PATCH liburing 0/4] test kernel allocated regions Pavel Begunkov
2024-11-20 23:39 ` [PATCH liburing 1/4] tests/reg-wait: test registering RO memory Pavel Begunkov
2024-11-20 23:39 ` [PATCH liburing 2/4] test/reg-wait: basic test + probing of kernel regions Pavel Begunkov
2024-11-20 23:39 ` [PATCH liburing 3/4] test/reg-wait: add allocation abstraction Pavel Begunkov
2024-11-20 23:39 ` [PATCH liburing 4/4] test/reg-wait: test kernel allocated regions Pavel Begunkov
2024-12-09 21:14 ` [PATCH liburing 0/4] " Pavel Begunkov
2024-12-09 21:16 ` 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=173377896392.323933.10570370010328158212.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