linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-virtualization@vger.kernel.org, georgezhang@vmware.com
Subject: Re: linux-next: Tree for Jan 10 (vmci)
Date: Thu, 10 Jan 2013 11:17:10 -0800	[thread overview]
Message-ID: <50EF13B6.9000809@infradead.org> (raw)
In-Reply-To: <20130110143241.041ef77011ef7b1f68ae5c61@canb.auug.org.au>

On 01/09/13 19:32, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20130109:
> 


on i386, when CONFIG_PCI is not enabled:

  CC [M]  drivers/misc/vmw_vmci/vmci_guest.o
drivers/misc/vmw_vmci/vmci_guest.c:58:20: error: array type has incomplete element type
drivers/misc/vmw_vmci/vmci_guest.c: In function 'vmci_enable_msix':
drivers/misc/vmw_vmci/vmci_guest.c:384:2: error: implicit declaration of function 'pci_enable_msix' [-Werror=implicit-function-declaration]
drivers/misc/vmw_vmci/vmci_guest.c: In function 'vmci_guest_probe_device':
drivers/misc/vmw_vmci/vmci_guest.c:466:2: error: implicit declaration of function 'pcim_enable_device' [-Werror=implicit-function-declaration]
drivers/misc/vmw_vmci/vmci_guest.c:592:2: error: implicit declaration of function 'pci_enable_msi' [-Werror=implicit-function-declaration]
drivers/misc/vmw_vmci/vmci_guest.c:654:3: error: implicit declaration of function 'pci_disable_msix' [-Werror=implicit-function-declaration]
drivers/misc/vmw_vmci/vmci_guest.c:656:3: error: implicit declaration of function 'pci_disable_msi' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[4]: *** [drivers/misc/vmw_vmci/vmci_guest.o] Error 1


Should all of vmci depend on PCI ??



-- 
~Randy

  parent reply	other threads:[~2013-01-10 19:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10  3:32 linux-next: Tree for Jan 10 Stephen Rothwell
2013-01-10 19:08 ` linux-next: Tree for Jan 10 (staging/sb105x) Randy Dunlap
2013-01-10 20:50   ` Steven Rostedt
2013-01-10 22:06     ` Randy Dunlap
2013-01-12  0:42       ` Greg Kroah-Hartman
2013-01-12  1:17         ` [PATCH] staging/sb105x: PARPORT config is not good enough must use PARPORT_PC Steven Rostedt
2013-01-10 19:17 ` Randy Dunlap [this message]
2013-01-10 19:28   ` linux-next: Tree for Jan 10 (vmci) Randy Dunlap

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=50EF13B6.9000809@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=georgezhang@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-virtualization@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).