linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Linus <torvalds@linux-foundation.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Joerg Roedel <joerg.roedel@amd.com>, Yu Zhao <yu.zhao@intel.com>
Subject: Re: linux-next: Tree for Oct 25 (pci/ats.c)
Date: Wed, 26 Oct 2011 11:37:07 -0700	[thread overview]
Message-ID: <4EA85353.4060101@xenotime.net> (raw)
In-Reply-To: <20111025203628.40a1b8a475e32053aa34dabe@canb.auug.org.au>

On 10/25/11 02:36, Stephen Rothwell wrote:
> Hi all,


When CONFIG_PCI_IOV is not enabled:
(probably because PCI_PRI selects PCI_ATS even when PCI_IOV is not
enabled)

drivers/pci/ats.c:37:5: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:44:11: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:45:5: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:55:5: error: redefinition of 'pci_enable_ats'
drivers/pci/ats.c:60:2: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:60:2: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:66:52: error: 'struct pci_dev' has no member named 'physfn'
drivers/pci/ats.c:68:3: error: 'struct pci_dev' has no member named 'sriov'
drivers/pci/ats.c:69:11: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:70:13: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:75:8: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:76:21: error: 'struct pci_dev' has no member named 'sriov'
drivers/pci/ats.c:90:32: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:92:5: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:102:6: error: redefinition of 'pci_disable_ats'
drivers/pci/ats.c:106:2: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:106:2: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:108:31: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:110:32: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:112:5: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:115:52: error: 'struct pci_dev' has no member named 'physfn'
drivers/pci/ats.c:117:3: error: 'struct pci_dev' has no member named 'sriov'
drivers/pci/ats.c:118:7: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:119:12: error: 'struct pci_dev' has no member named 'ats'
drivers/pci/ats.c:121:21: error: 'struct pci_dev' has no member named 'sriov'
drivers/pci/ats.c:141:5: error: redefinition of 'pci_ats_queue_depth'
drivers/pci/ats.c:149:9: error: 'struct pci_dev' has no member named 'ats'
next-2011-1025/drivers/pci/ats.c:150:13: error: 'struct pci_dev' has no member named 'ats'



Looks like ats.c also needs to #include <linux/export.h>:

drivers/pci/ats.c:96:1: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL' [-Wimplicit-int]
drivers/pci/ats.c:127:1: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL' [-Wimplicit-int]
drivers/pci/ats.c:161:1: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL' [-Wimplicit-int]
drivers/pci/ats.c:194:1: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL' [-Wimplicit-int]
drivers/pci/ats.c:215:1: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL' [-Wimplicit-int]
drivers/pci/ats.c:236:1: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL' [-Wimplicit-int]
drivers/pci/ats.c:264:1: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL' [-Wimplicit-int]
drivers/pci/ats.c:295:1: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL' [-Wimplicit-int]
drivers/pci/ats.c:325:1: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL' [-Wimplicit-int]

-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2011-10-26 18:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25  9:36 linux-next: Tree for Oct 25 Stephen Rothwell
2011-10-25  9:43 ` Stephen Rothwell
2011-10-25 10:42 ` Stephen Rothwell
2011-10-26  0:34 ` linux-next: Tree for Oct 25 (agp/intel-gtt.c) Randy Dunlap
2011-11-03 21:21   ` Randy Dunlap
2011-10-26  0:42 ` linux-next: Tree for Oct 25 (crypto) Randy Dunlap
2011-10-26  6:27   ` Herbert Xu
2011-10-26 12:33     ` Stefan Richter
2011-10-26 16:27       ` Randy Dunlap
2011-10-26 17:15         ` Stefan Richter
2011-10-27  7:05     ` Valdis.Kletnieks
2011-10-27  7:45       ` Herbert Xu
2011-10-29 23:20         ` Valdis.Kletnieks
2011-10-26 18:26 ` linux-next: Tree for Oct 25 (mfd/ab8500) Randy Dunlap
2011-10-30 23:04   ` Samuel Ortiz
2011-10-26 18:37 ` Randy Dunlap [this message]
2011-11-10 13:09   ` linux-next: Tree for Oct 25 (pci/ats.c) Ingo Molnar
2011-10-26 18:39 ` linux-next: Tree for Oct 25 (target) Randy Dunlap
2011-10-26 19:53   ` Nicholas A. Bellinger
2011-10-26 20:40     ` Stephen Rothwell
2011-10-26 20:42       ` Nicholas A. Bellinger
2011-10-26 18:47 ` linux-next: Tree for Oct 25 (sb_edac.c) 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=4EA85353.4060101@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=yu.zhao@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;
as well as URLs for NNTP newsgroup(s).