From: Stefan Hajnoczi <[email protected]>
To: Dominique Martinet <[email protected]>
Cc: Stefan Hajnoczi <[email protected]>,
Jens Axboe <[email protected]>,
Stefano Garzarella <[email protected]>,
Aarushi Mehta <[email protected]>,
Julia Suvorova <[email protected]>, Kevin Wolf <[email protected]>,
Hanna Reitz <[email protected]>,
qemu block <[email protected]>,
qemu-devel <[email protected]>,
Filipe Manana <[email protected]>,
[email protected]
Subject: Re: [PATCH v2] io_uring: fix short read slow path
Date: Wed, 6 Jul 2022 08:51:36 +0100 [thread overview]
Message-ID: <YsU/[email protected]> (raw)
In-Reply-To: <[email protected]>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
On Wed, Jul 06, 2022 at 04:26:59PM +0900, Dominique Martinet wrote:
> Stefan Hajnoczi wrote on Wed, Jul 06, 2022 at 08:17:42AM +0100:
> > Great! I've already queued your fix.
>
> Thanks!
>
> > Do you want to send a follow-up that updates the comment?
>
> I don't think I'd add much value at this point, leaving it to you unless
> you really would prefer me to send it.
That's fine. I'll send a patch. Thanks!
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-07-06 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[email protected]>
[not found] ` <[email protected]>
[not found] ` <20220630154921.ekl45dzer6x4mkvi@sgarzare-redhat>
[not found] ` <[email protected]>
2022-07-05 13:28 ` [PATCH v2] io_uring: fix short read slow path Stefan Hajnoczi
2022-07-05 19:23 ` Jens Axboe
2022-07-06 7:16 ` Stefan Hajnoczi
2022-07-05 22:52 ` Dominique Martinet
2022-07-06 7:17 ` Stefan Hajnoczi
2022-07-06 7:26 ` Dominique Martinet
2022-07-06 7:51 ` Stefan Hajnoczi [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=YsU/[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[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