xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Martinx - ジェームズ" <thiagocmartinsc@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Please test xen/stable-2.6.32.x in xen.git
Date: Thu, 1 Apr 2010 16:06:31 -0400	[thread overview]
Message-ID: <20100401200630.GA15810@phenom.dumpdata.com> (raw)
In-Reply-To: <o2h6b7f6eb1004011055rae49d0f0r60c3f1bbda78b301@mail.gmail.com>

On Thu, Apr 01, 2010 at 02:55:45PM -0300, Martinx - ジェームズ wrote:
> Hi!
> 
>  I can't compile it:
> 
>   CC      drivers/pci/xen-pcifront.o
> drivers/pci/xen-pcifront.c:373: error: variable ‘pci_frontend_ops’ has
> initializer but incomplete type
> drivers/pci/xen-pcifront.c:374: error: unknown field ‘enable_msi’ specified
> in initializer
> drivers/pci/xen-pcifront.c:374: warning: excess elements in struct
> initializer
> drivers/pci/xen-pcifront.c:374: warning: (near initialization for
> ‘pci_frontend_ops’)
> drivers/pci/xen-pcifront.c:375: error: unknown field ‘disable_msi’ specified
> in initializer
> drivers/pci/xen-pcifront.c:375: warning: excess elements in struct
> initializer
> drivers/pci/xen-pcifront.c:375: warning: (near initialization for
> ‘pci_frontend_ops’)
> drivers/pci/xen-pcifront.c:376: error: unknown field ‘enable_msix’ specified
> in initializer
> drivers/pci/xen-pcifront.c:376: warning: excess elements in struct
> initializer
> drivers/pci/xen-pcifront.c:376: warning: (near initialization for
> ‘pci_frontend_ops’)
> drivers/pci/xen-pcifront.c:377: error: unknown field ‘disable_msix’
> specified in initializer
> drivers/pci/xen-pcifront.c:377: warning: excess elements in struct
> initializer
> drivers/pci/xen-pcifront.c:377: warning: (near initialization for
> ‘pci_frontend_ops’)
> drivers/pci/xen-pcifront.c: In function ‘pci_frontend_registrar’:
> drivers/pci/xen-pcifront.c:383: error: ‘xen_pci_frontend’ undeclared (first
> use in this function)
> drivers/pci/xen-pcifront.c:383: error: (Each undeclared identifier is
> reported only once
> drivers/pci/xen-pcifront.c:383: error: for each function it appears in.)
> make[2]: *** [drivers/pci/xen-pcifront.o] Error 1
> make[1]: *** [drivers/pci] Error 2
> make: *** [drivers] Error 2

I have this fixed in the pv/pcifront-2.6.33 branch but forgot to
back-port. This is what I think you need:

diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig
index 7802fcd..831365d 100644
--- a/drivers/pci/Kconfig
+++ b/drivers/pci/Kconfig
@@ -53,7 +53,7 @@ config PCI_STUB
 
 config XEN_PCIDEV_FRONTEND
         tristate "Xen PCI Frontend"
-        depends on XEN && PCI && X86
+        depends on X86 && XEN_PCI_PASSTHROUGH
         select HOTPLUG
 	select XEN_XENBUS_FRONTEND
 	default y

  parent reply	other threads:[~2010-04-01 20:06 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-31 17:58 Please test xen/stable-2.6.32.x in xen.git Jeremy Fitzhardinge
2010-03-31 18:14 ` Stefan Kuhne
2010-03-31 19:06   ` Jeremy Fitzhardinge
2010-03-31 20:26     ` Stefan Kuhne
2010-03-31 20:31       ` Jeremy Fitzhardinge
2010-04-01  7:38         ` Stefan Kuhne
2010-04-01 17:55           ` Martinx - ジェームズ
2010-04-01 19:35             ` Jeremy Fitzhardinge
2010-04-01 20:29               ` Martinx - ジェームズ
2010-04-01 20:06             ` Konrad Rzeszutek Wilk [this message]
2010-04-01 19:06           ` Jeremy Fitzhardinge
2010-04-01 19:55             ` Stefan Kuhne
2010-04-01 20:08               ` Jeremy Fitzhardinge
2010-04-01 21:04                 ` Stefan Kuhne
2010-04-01 21:49                   ` Jeremy Fitzhardinge
2010-04-01 21:54                     ` Stefan Kuhne
2010-04-01 22:02                       ` Jeremy Fitzhardinge
2010-04-01 22:08                         ` Stefan Kuhne
2010-04-02 10:51                       ` Pasi Kärkkäinen
2010-04-03 14:10                         ` X-Server doesn't start under Xen 4.0-rc9 & 2.6.31.11 pvops on top of F12 Boris Derzhavets
2010-04-06 18:30                           ` Jeremy Fitzhardinge
2010-04-06 21:37                             ` Boris Derzhavets
2010-04-06 22:01                               ` Jeremy Fitzhardinge
2010-04-06 22:40                                 ` Mark Hurenkamp
2010-04-06 22:41                                   ` Jeremy Fitzhardinge
2010-04-06 23:08                                     ` Mark Hurenkamp
2010-04-07 11:30                                 ` Boris Derzhavets
2010-04-07 16:20                                   ` Boris Derzhavets
2010-04-06 22:38                           ` Mark Hurenkamp
2010-04-06 22:40                             ` Jeremy Fitzhardinge
2010-04-02 13:11                 ` Bugs in 2.6.31.12-pvops Carsten Schiers
2010-04-02 18:11                   ` Jeremy Fitzhardinge
2010-04-08  0:30               ` Please test xen/stable-2.6.32.x in xen.git Konrad Rzeszutek Wilk
     [not found]                 ` <4BBD9DC7.603@access.denied>
2010-04-08 14:59                   ` Konrad Rzeszutek Wilk
2010-03-31 18:45 ` Pasi Kärkkäinen
2010-03-31 20:10 ` Olivier B.
2010-03-31 20:32   ` Olivier B.
2010-03-31 20:35   ` Jeremy Fitzhardinge
2010-03-31 20:43     ` Olivier B.
2010-04-05 16:53 ` Guillaume Rousse

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=20100401200630.GA15810@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=thiagocmartinsc@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).