From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Tony Luck <tony.luck@intel•com>
Cc: Gong Chen <gong.chen@linux•intel.com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: build warnings after merge of the ia64 tree
Date: Wed, 16 Jul 2014 12:00:00 +1000 [thread overview]
Message-ID: <20140716120000.3523239b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
Hi all,
After merging the ia64 tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings (though presumably it started
yesterday):
In file included from include/ras/ras_event.h:11:0,
from drivers/ras/ras.c:13:
include/linux/aer.h:42:58: warning: 'struct pci_dev' declared inside parameter list
static inline int pci_enable_pcie_error_reporting(struct pci_dev *dev)
^
include/linux/aer.h:42:58: warning: its scope is only this definition or declaration, which is probably not what you want
include/linux/aer.h:46:59: warning: 'struct pci_dev' declared inside parameter list
static inline int pci_disable_pcie_error_reporting(struct pci_dev *dev)
^
include/linux/aer.h:50:65: warning: 'struct pci_dev' declared inside parameter list
static inline int pci_cleanup_aer_uncorrect_error_status(struct pci_dev *dev)
^
include/linux/aer.h:57:14: warning: 'struct pci_dev' declared inside parameter list
struct aer_capability_regs *aer);
^
Introduced by commit 76ac8275f296 ("trace, RAS: Add basic RAS trace
event") and following patches.
So, presumably, aer.h either needs to include pci.h or, at least, have a
struct pci_dev;
line in it.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2014-07-16 2:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 2:00 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-12-17 0:23 linux-next: build warnings after merge of the ia64 tree Stephen Rothwell
2010-12-17 0:43 ` Luck, Tony
2010-12-17 0:50 ` Luck, Tony
2010-12-17 0:59 ` Stephen Rothwell
2010-12-17 19:58 ` Luck, Tony
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=20140716120000.3523239b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=gong.chen@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tony.luck@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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