From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Fix declerations that should be in kvm-common.h & not in kvm-x86.h
Date: Sun, 11 Nov 2007 12:05:30 +0200 [thread overview]
Message-ID: <4736D3EA.3010707@qumranet.com> (raw)
In-Reply-To: <f87e6f60ddd69cb0ee4e.1194543933@thinkpad>
Jerone Young wrote:
> # HG changeset patch
> # User Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> # Date 1194543880 21600
> # Node ID f87e6f60ddd69cb0ee4e0bbcaed657d2f12311ce
> # Parent d6fa0d16fa60ee5083877fec698b69cea840d0b0
> Fix declerations that should be in kvm-common.h & not in kvm-x86.h
>
> During the first phase of the refactoring these function declerations
> where not moved over to the kvm-common.h.
>
> Function decleartions include:
> kvm_alloc_kernel_memory
> kvm_alloc_userspace_memory
> kvm_create_kernel_phys_mem
> kvm_show_code
> kvm_run_abi10
>
>
Aren't most of these x86 specific?
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-11-11 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 17:45 [PATCH] Fix declerations that should be in kvm-common.h & not in kvm-x86.h Jerone Young
2007-11-11 10:05 ` Avi Kivity [this message]
[not found] ` <4736D3EA.3010707-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-12 3:59 ` Jerone Young
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=4736D3EA.3010707@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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