From: Eric Blake <eblake@redhat.com>
To: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"fam@euphon.net" <fam@euphon.net>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Denis Lunev <den@virtuozzo.com>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"stefanha@redhat.com" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block: workaround for unaligned byte range in fallocate()
Date: Tue, 27 Aug 2019 08:50:03 -0500 [thread overview]
Message-ID: <2ed4f9de-9e2d-0b6f-0248-c213c1ac9668@redhat.com> (raw)
In-Reply-To: <8a642371-bbd7-26bd-f54b-576ce49c05d2@virtuozzo.com>
[-- Attachment #1.1: Type: text/plain, Size: 550 bytes --]
On 8/27/19 7:39 AM, Andrey Shinkevich wrote:
>
>
>>>
>>
>> Reviewed-by: Eric Blake <eblake@redhat.com>
>>
> Eric,
> If you are good to take this patch to your branch with your corrections,
> please let us know. Otherwise, I will send the v2 with your corrections.
Since I based my fast-zero patches on top of this, I'm fine making the
corrections locally and queuing this patch through my NBD tree.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-08-27 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 18:31 [Qemu-devel] [PATCH] block: workaround for unaligned byte range in fallocate() Andrey Shinkevich
2019-08-22 18:55 ` Vladimir Sementsov-Ogievskiy
2019-08-22 19:10 ` Vladimir Sementsov-Ogievskiy
2019-08-22 21:09 ` Eric Blake
2019-08-23 12:07 ` Andrey Shinkevich
2019-08-27 12:35 ` Denis V. Lunev
2019-08-27 12:39 ` Andrey Shinkevich
2019-08-27 13:50 ` Eric Blake [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=2ed4f9de-9e2d-0b6f-0248-c213c1ac9668@redhat.com \
--to=eblake@redhat.com \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.com \
/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;
as well as URLs for NNTP newsgroup(s).