From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH liburing 1/1] tests/fd-pass: close rings
Date: Sun, 05 Mar 2023 07:35:30 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <2514ac14bffdffe0a78fd51c41698deb20d54cc4.1677993404.git.asml.silence@gmail.com>
On Sun, 05 Mar 2023 05:16:57 +0000, Pavel Begunkov wrote:
> Don't leak rings from test(), we call it several times and have a good
> number of open rings lingering during the test for no good reason.
>
>
Applied, thanks!
[1/1] tests/fd-pass: close rings
commit: 3533273acbacdc5b120dce12d3aab5c8e56e6186
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-03-05 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 5:16 [PATCH liburing 1/1] tests/fd-pass: close rings Pavel Begunkov
2023-03-05 14: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=167802693059.46805.5440720987736674735.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