From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Hollis Blanchard <hollisb-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 0 of 2] A couple ifdefs
Date: Wed, 16 Jan 2008 10:03:25 +0200 [thread overview]
Message-ID: <478DBA4D.7060408@qumranet.com> (raw)
In-Reply-To: <patchbomb.1200434384@basalt>
Hollis Blanchard wrote:
> These small ifdefs are necessary for integration of the PowerPC port.
>
>
Only patch 2 of 2 made it.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-01-16 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 21:59 [PATCH 0 of 2] A couple ifdefs Hollis Blanchard
2008-01-15 21:59 ` [PATCH 1 of 2] Define and use CONFIG_KVM_HAS_PIO so that we don't need pio_data in kvm_arch_vcpu Hollis Blanchard
2008-01-20 13:15 ` Avi Kivity
[not found] ` <47934974.2020107-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-24 12:59 ` Carsten Otte
[not found] ` <47988BA1.80507-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2008-01-24 13:14 ` Avi Kivity
2008-01-15 21:59 ` [PATCH 2 of 2] Use CONFIG_PREEMPT_NOTIFIERS around struct preempt_notifier Hollis Blanchard
2008-01-16 8:08 ` Avi Kivity
[not found] ` <478DBB95.6030005-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-16 16:23 ` Hollis Blanchard
2008-01-16 8:03 ` Avi Kivity [this message]
[not found] ` <478DBA4D.7060408-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-16 9:24 ` [PATCH 0 of 2] A couple ifdefs Christian Ehrhardt
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=478DBA4D.7060408@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=hollisb-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