From: Avi Kivity <avi@redhat.com>
To: "Zhang, Yang" <yang.zhang@intel.com>
Cc: "kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>
Subject: Re: [PATCH] KVM : Qemu: update call pci_nic_init
Date: Thu, 15 Jan 2009 11:26:33 +0200 [thread overview]
Message-ID: <496F0149.1090709@redhat.com> (raw)
In-Reply-To: <10C63FAD690C13458F0B32BCED571F1403D74F21@pdsmsx502.ccr.corp.intel.com>
Zhang, Yang wrote:
> Hi
> As the definition pci_nic_init has modified, this patch update the corresponding calling in ipf_init1().
>
> From 53a66f524a6c2215d61da797cca4b7b1acbb1266 Mon Sep 17 00:00:00 2001
> From: Yang <yang.zhang@intel.com>
> Date: Thu, 15 Jan 2009 13:09:43 +0800
> Subject: [PATCH] KVM : Qemu: update call pci_nic_init
>
> update call pci_nic_init in ipf_init1
>
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-01-15 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 7:36 [PATCH] KVM : Qemu: update call pci_nic_init Zhang, Yang
2009-01-15 8:31 ` Mark McLoughlin
2009-01-15 8:49 ` Zhang, Xiantao
2009-01-15 9:26 ` Avi Kivity [this message]
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=496F0149.1090709@redhat.com \
--to=avi@redhat.com \
--cc=kvm-ia64@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=xiantao.zhang@intel.com \
--cc=yang.zhang@intel.com \
/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