From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] memory: synchronize dirty bitmap before unmapping a range
Date: Mon, 01 Aug 2011 12:32:44 +0300 [thread overview]
Message-ID: <4E3672BC.9000807@redhat.com> (raw)
In-Reply-To: <4E367230.6020705@redhat.com>
On 08/01/2011 12:30 PM, Avi Kivity wrote:
>
>> It does not link here due to forgotten rwhandler in Makefile.target.
>>
>
> I probably still have it in my tree, will update and re-push.
done now.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-08-01 9:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 19:47 [Qemu-devel] [PATCH] memory: synchronize dirty bitmap before unmapping a range Avi Kivity
2011-08-01 7:34 ` Jan Kiszka
2011-08-01 7:52 ` Jan Kiszka
2011-08-01 8:16 ` Avi Kivity
2011-08-01 9:05 ` Jan Kiszka
2011-08-01 9:30 ` Avi Kivity
2011-08-01 9:32 ` Avi Kivity [this message]
2011-08-01 9:45 ` Avi Kivity
2011-08-01 10:21 ` Jan Kiszka
2011-08-01 10:27 ` Avi Kivity
2011-08-05 16:47 ` Anthony Liguori
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=4E3672BC.9000807@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.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 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).