From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: Qemu: Change default max_cpus to 255.
Date: Sun, 19 Oct 2008 09:38:20 +0000 [thread overview]
Message-ID: <48FB000C.3020909@redhat.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC01B4859A@pdsmsx415.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> Hi, Avi
> Fix the issue caused by latest merge with Qemu upstream.
> Thanks
> Xiantao
> From 4f921522258c2200353102d3813a30af9d753ae0 Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Fri, 17 Oct 2008 14:26:57 +0800
> Subject: [PATCH] Qemu: Change default max_cpus to 255.
>
> Initilize the field max_cpus of machine to 255 for ia64.
> Use C99 style to intilize machine structure.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: kvm-ia64@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: Qemu: Change default max_cpus to 255.
Date: Sun, 19 Oct 2008 11:38:20 +0200 [thread overview]
Message-ID: <48FB000C.3020909@redhat.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC01B4859A@pdsmsx415.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> Hi, Avi
> Fix the issue caused by latest merge with Qemu upstream.
> Thanks
> Xiantao
> From 4f921522258c2200353102d3813a30af9d753ae0 Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Fri, 17 Oct 2008 14:26:57 +0800
> Subject: [PATCH] Qemu: Change default max_cpus to 255.
>
> Initilize the field max_cpus of machine to 255 for ia64.
> Use C99 style to intilize machine structure.
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-10-19 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 7:17 Qemu: Change default max_cpus to 255 Zhang, Xiantao
2008-10-17 7:17 ` Zhang, Xiantao
2008-10-19 9:38 ` Avi Kivity [this message]
2008-10-19 9:38 ` 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=48FB000C.3020909@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.