From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [PATCH] KVM: Qemu: Fix ia64 boot failure and build issue.
Date: Mon, 13 Apr 2009 08:19:03 +0000 [thread overview]
Message-ID: <49E2F577.6070003@redhat.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC23281BA54@pdsmsx503.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> commit 30a96c404b41d4091781c33cfdf5384a7b6b655e
> Author: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Tue Apr 7 09:58:25 2009 -0400
>
> KVM: Qemu: Fix ia64 boot failure and build issue.
>
> 1. Remove vga_bios_init for arch ia64, and doesn't need it now.
> 2. Fix build issue due to lacking of header file.
>
Thanks, I split the patch into two and applied.
--
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-ia64@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: Qemu: Fix ia64 boot failure and build issue.
Date: Mon, 13 Apr 2009 11:19:03 +0300 [thread overview]
Message-ID: <49E2F577.6070003@redhat.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC23281BA54@pdsmsx503.ccr.corp.intel.com>
Zhang, Xiantao wrote:
> commit 30a96c404b41d4091781c33cfdf5384a7b6b655e
> Author: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Tue Apr 7 09:58:25 2009 -0400
>
> KVM: Qemu: Fix ia64 boot failure and build issue.
>
> 1. Remove vga_bios_init for arch ia64, and doesn't need it now.
> 2. Fix build issue due to lacking of header file.
>
Thanks, I split the patch into two and applied.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-13 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 6:36 [PATCH] KVM: Qemu: Fix ia64 boot failure and build issue Zhang, Xiantao
2009-04-13 6:36 ` Zhang, Xiantao
2009-04-13 8:19 ` Avi Kivity [this message]
2009-04-13 8:19 ` 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=49E2F577.6070003@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.