From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: "bderzhavets@yahoo.com" <bderzhavets@yahoo.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] fs-backend: fix compile problems
Date: Wed, 18 Mar 2009 14:19:50 +0000 [thread overview]
Message-ID: <49C10306.3080106@eu.citrix.com> (raw)
In-Reply-To: <772991.29608.qm@web56105.mail.re3.yahoo.com>
Boris Derzhavets wrote:
> Removed unresolved reference in
> /usr/src/xen-unstable.hg/tools/ioemu-dir/vl.c:5898: undefined reference
> to `pci_emulation_add'
>
> /* for (i = 0; i < nb_pci_emulation; i++) {
> if(pci_emulation_add(pci_emulation_config_text[i]) < 0) {
> fprintf(stderr, "Warning: could not add PCI device %s\n",
> pci_emulation_config_text[i]);
> }
> }
> */
>
> "make tools" completed OK.
> Is it acceptable ?
>
I think we are missing an ifdef CONFIG_PASSTHROUGH
diff --git a/vl.c b/vl.c
index 9b9f7d5..6c0ffb3 100644
--- a/vl.c
+++ b/vl.c
@@ -5894,12 +5894,14 @@ int main(int argc, char **argv, char **envp)
}
}
+#ifdef CONFIG_PASSTHROUGH
for (i = 0; i < nb_pci_emulation; i++) {
if(pci_emulation_add(pci_emulation_config_text[i]) < 0) {
fprintf(stderr, "Warning: could not add PCI device %s\n",
pci_emulation_config_text[i]);
}
}
+#endif
if (strlen(direct_pci_str) > 0)
direct_pci = direct_pci_str;
next prev parent reply other threads:[~2009-03-18 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 12:03 [PATCH] fs-backend: fix compile problems Stefano Stabellini
2009-03-18 14:03 ` Boris Derzhavets
2009-03-18 14:12 ` Stefano Stabellini
2009-03-18 14:18 ` Boris Derzhavets
2009-03-18 14:19 ` Stefano Stabellini [this message]
2009-03-18 14:48 ` Boris Derzhavets
2009-03-18 14:53 ` Boris Derzhavets
2009-03-18 15:00 ` Keir Fraser
2009-03-18 16:13 ` Boris Derzhavets
2009-03-18 17:26 ` Keir Fraser
2009-03-18 21:21 ` Karthik G Balaji
2009-03-18 15:01 ` Jiang, Yunhong
-- strict thread matches above, loose matches on Subject: below --
2009-03-18 16:24 Boris Derzhavets
2009-03-18 16:41 ` Boris Derzhavets
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=49C10306.3080106@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=bderzhavets@yahoo.com \
--cc=xen-devel@lists.xensource.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 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.