From: Jens Axboe <[email protected]>
To: Wojciech Lukowicz <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH 0/2] fixes for removing provided buffers
Date: Sat, 1 Apr 2023 17:20:08 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 4/1/23 1:50 PM, Wojciech Lukowicz wrote:
> Hi,
>
> Two fixes for removing provided buffers. They are in the same area, but
> otherwise unrelated. I'll send a liburing test for the first one
> shortly.
Looks good, thanks for sending these in!
--
Jens Axboe
next prev parent reply other threads:[~2023-04-01 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 19:50 [PATCH 0/2] fixes for removing provided buffers Wojciech Lukowicz
2023-04-01 19:50 ` [PATCH 1/2] io_uring: fix return value when " Wojciech Lukowicz
2023-04-01 19:50 ` [PATCH 2/2] io_uring: fix memory leak " Wojciech Lukowicz
2023-04-01 23:20 ` Jens Axboe [this message]
2023-04-01 23:20 ` [PATCH 0/2] fixes for " Jens Axboe
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 \
[email protected] \
[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