From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/2] Plan obsolescense of exec.c memory functions
Date: Mon, 19 Dec 2011 17:06:04 +0200 [thread overview]
Message-ID: <4EEF52DC.6080301@redhat.com> (raw)
In-Reply-To: <4EEF51E5.6070700@codemonkey.ws>
On 12/19/2011 05:01 PM, Anthony Liguori wrote:
> On 12/15/2011 07:35 AM, Avi Kivity wrote:
>> Exile some exec.c functions to a private header, to prevent
>> accidental reuse.
>>
>> Please pull from
>>
>> git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git
>> memory/exec-obsolete
>
> This breaks the Xen build. Perhaps we need to merge your patches to
> convert Xen to the memory API first?
>
> cc1: warnings being treated as errors
> /home/anthony/git/qemu/xen-all.c: In function ‘xen_ram_init’:
> /home/anthony/git/qemu/xen-all.c:169:5: error: implicit declaration of
> function ‘cpu_register_physical_memory’
> /home/anthony/git/qemu/xen-all.c:169:5: error: nested extern
> declaration of ‘cpu_register_physical_memory’
> make[1]: *** [xen-all.o] Error 1
Yeah, I'll redo and repost.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-19 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 13:35 [Qemu-devel] [PULL 0/2] Plan obsolescense of exec.c memory functions Avi Kivity
2011-12-15 13:35 ` [Qemu-devel] [PATCH 1/2] etraxfs_eth: drop bogus cpu_unregister_io_memory() Avi Kivity
2011-12-15 13:35 ` [Qemu-devel] [PATCH 2/2] memory: move obsolete exec.c functions to a private header Avi Kivity
2011-12-15 14:21 ` [Qemu-devel] [PULL 0/2] Plan obsolescense of exec.c memory functions Paolo Bonzini
2011-12-15 14:22 ` Avi Kivity
2011-12-15 14:26 ` Anthony Liguori
2011-12-19 15:01 ` Anthony Liguori
2011-12-19 15:06 ` Avi Kivity [this message]
2011-12-19 15:34 ` Avi Kivity
2011-12-19 16:15 ` Anthony Liguori
2011-12-19 17:12 ` Avi Kivity
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=4EEF52DC.6080301@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--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).