From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: John Snow <jsnow@redhat.com>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
Denis Lunev <den@virtuozzo.com>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"armbru@redhat.com" <armbru@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/3] backup fixes for 4.1?
Date: Wed, 31 Jul 2019 10:29:45 +0000 [thread overview]
Message-ID: <877c1717-738e-f3a2-2cb4-3aa11e738fc0@virtuozzo.com> (raw)
In-Reply-To: <c78b645a-e79b-1335-0e6e-44db4953417d@redhat.com>
30.07.2019 21:41, John Snow wrote:
>
>
> On 7/30/19 12:32 PM, Vladimir Sementsov-Ogievskiy wrote:
>> Hi all!
>>
>> Here are two small fixes.
>>
>> 01 is not a degradation at all, so it's OK for 4.2
>> 02 is degradation of 3.0, so it's possibly OK for 4.2 too,
>> but it seems to be real bug and fix is very simple, so,
>> may be 4.1 is better
>>
>> Or you may take the whole series to 4.1 if you want.
>>
>
> I think (1) and (2) can go in for stable after review, but they're not
> crucial for 4.1 especially at this late of a stage. Should be cataclysms
> only right now.
>
> --js
>
I can rebase it than on your bitmaps branch. Or, if we want it for stable, maybe,
I shouldn't?
--
Best regards,
Vladimir
next prev parent reply other threads:[~2019-07-31 10:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 16:32 [Qemu-devel] [PATCH 0/3] backup fixes for 4.1? Vladimir Sementsov-Ogievskiy
2019-07-30 16:32 ` [Qemu-devel] [PATCH 1/3] block/backup: deal with zero detection Vladimir Sementsov-Ogievskiy
2019-07-30 18:40 ` John Snow
2019-07-31 10:01 ` Vladimir Sementsov-Ogievskiy
2019-07-31 13:45 ` John Snow
2019-08-01 11:18 ` Max Reitz
2019-08-01 11:18 ` Max Reitz
2019-07-30 16:32 ` [Qemu-devel] [PATCH 2/3] block/backup: disable copy_range for compressed backup Vladimir Sementsov-Ogievskiy
2019-07-30 18:22 ` John Snow
2019-07-31 13:51 ` Vladimir Sementsov-Ogievskiy
2019-08-01 11:20 ` Max Reitz
2019-08-05 16:05 ` Max Reitz
2019-07-30 16:32 ` [Qemu-devel] [PATCH 3/3] block/backup: refactor write_flags Vladimir Sementsov-Ogievskiy
2019-07-30 18:28 ` John Snow
2019-07-31 16:01 ` Vladimir Sementsov-Ogievskiy
2019-08-01 11:28 ` Max Reitz
2019-08-01 11:32 ` Vladimir Sementsov-Ogievskiy
2019-08-01 11:37 ` Max Reitz
2019-08-01 12:02 ` Vladimir Sementsov-Ogievskiy
2019-08-01 12:21 ` Max Reitz
2019-08-01 12:40 ` Vladimir Sementsov-Ogievskiy
2019-08-01 11:28 ` Max Reitz
2019-07-30 18:41 ` [Qemu-devel] [PATCH 0/3] backup fixes for 4.1? John Snow
2019-07-31 10:29 ` Vladimir Sementsov-Ogievskiy [this message]
2019-07-31 13:46 ` John Snow
2019-08-07 23:52 ` John Snow
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=877c1717-738e-f3a2-2cb4-3aa11e738fc0@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@virtuozzo.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.