From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@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>,
"famz@redhat.com" <famz@redhat.com>,
Denis Lunev <den@virtuozzo.com>,
"jcody@redhat.com" <jcody@redhat.com>,
"mreitz@redhat.com" <mreitz@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] ping2 Re: [PATCH v4 0/8] dirty-bitmap: rewrite bdrv_dirty_iter_next_area
Date: Thu, 13 Dec 2018 13:18:34 -0500 [thread overview]
Message-ID: <091d787b-c2e8-6296-792f-6223015f0d0e@redhat.com> (raw)
In-Reply-To: <c4c5d8ec-eb90-915c-03d3-95c7517b4b57@virtuozzo.com>
On 12/13/18 6:07 AM, Vladimir Sementsov-Ogievskiy wrote:
> 12.12.2018 23:41, John Snow wrote:
>>
>>
>> On 12/12/18 4:27 AM, Vladimir Sementsov-Ogievskiy wrote:
>>> ping. No dependencies, apply to master.
>>>
>>
>> Sure thing.
>>
>> Staged to jsnow/bitmaps.
>
>
> Thank you!
>
> Oops, I've missed your email about s/firt_dirty_off/first_dirty_off
>
> I can resend, or you can fix in your branch, as you prefer.
> The variable touches two commits in jsnow/bitmaps:
>
Whoops, I forgot too. I just remember that I was waiting on a requisite
and it got lost so I was in a hurry to stage it for you. I'll just
squash any fixes in.
I'll try to send the PR when the qemu-img bitmap info patch is ready,
alongside my series to drop the x-prefix (and adjust the merge API.)
Anything else urgent for the start of the 4.0 window before we all
disappear on holiday break?
--js
> commit f235204c39dd5ce122666d87f18005264eb56e51
> Author: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Date: Mon Sep 17 17:57:27 2018 +0300
>
> dirty-bitmap: add bdrv_dirty_bitmap_next_dirty_area
>
> and the last one:
>
> commit 7f73174ca1c8a92e4a5139b35f2a2273f59ce29b (jnsnow/bitmaps)
> Author: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Date: Mon Sep 17 17:57:32 2018 +0300
>
> Revert "hbitmap: Add @advance param to hbitmap_iter_next()"
>
>
>
>
next prev parent reply other threads:[~2018-12-13 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180917145732.48590-1-vsementsov@virtuozzo.com>
2018-10-11 15:38 ` [Qemu-devel] ping Re: [PATCH v4 0/8] dirty-bitmap: rewrite bdrv_dirty_iter_next_area Vladimir Sementsov-Ogievskiy
2018-12-12 9:27 ` [Qemu-devel] ping2 " Vladimir Sementsov-Ogievskiy
2018-12-12 20:41 ` John Snow
2018-12-13 11:07 ` Vladimir Sementsov-Ogievskiy
2018-12-13 18:18 ` John Snow [this message]
2018-12-13 20:06 ` Denis Lunev
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=091d787b-c2e8-6296-792f-6223015f0d0e@redhat.com \
--to=jsnow@redhat.com \
--cc=den@virtuozzo.com \
--cc=famz@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).