From: Bjorn Helgaas <bhelgaas@google.com>
To: Mike Qiu <qiudayu@linux.vnet.ibm.com>
Cc: linux-pci@vger.kernel.org,
Tuomas Tynkkynen <ttynkkynen@nvidia.com>,
Gavin Shan <gwshan@linux.vnet.ibm.com>,
Randy Dunlap <rdunlap@infradead.org>,
gong.chen@linux.intel.com, Lance Ortiz <lance.ortiz@hp.com>,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH] Fix build warnings in aer.h
Date: Mon, 21 Jul 2014 20:38:13 -0600 [thread overview]
Message-ID: <20140722023813.GA27601@google.com> (raw)
In-Reply-To: <1405498124-11519-1-git-send-email-qiudayu@linux.vnet.ibm.com>
[+cc Tuomas, Randy, Gavin, Gong, Lance, Tony]
On Wed, Jul 16, 2014 at 04:08:44AM -0400, Mike Qiu wrote:
> build log:
>
> In file included from include/ras/ras_event.h:11:0,
> from drivers/ras/ras.c:13:
> include/linux/aer.h:42:129: warning: ‘struct pci_dev’
> declared inside parameter list [enabled by default]
>
> include/linux/aer.h:42:129: warning: its scope is only
> this definition or declaration, which is probably not
> what you want [enabled by default]
>
> include/linux/aer.h:46:130: warning: ‘struct pci_dev’
> declared inside parameter list [enabled by default]
>
> include/linux/aer.h:50:136: warning: ‘struct pci_dev’
> declared inside parameter list [enabled by default]
>
> include/linux/aer.h:57:14: warning: ‘struct pci_dev’
> declared inside parameter list [enabled by default]
>
> Signed-off-by: Mike Qiu <qiudayu@linux.vnet.ibm.com>
OK, so the problem doesn't occur on x86 because there we have a struct
pci_dev declaration reached earlier via:
drivers/ras/ras.c
include/ras/ras_event.h
include/linux/edac.h
include/linux/device.h
include/linux/gfp.h
arch/x86/include/asm/mmzone.h
arch/x86/include/asm/mmzone_64.h
arch/x86/include/asm/smp.h
arch/x86/include/asm/mpspec.h
arch/x86/include/asm/x86_init.h
struct pci_dev;
include/linux/aer.h
... pci_enable_pcie_error_reporting(struct pci_dev *dev);
You're building powerpc, which doesn't have the same pci_dev
declaration in the arch header files, so you see the declaration
problem in aer.h.
I could apply your fix, but it should go in v3.16 along with the commit
(0a2409aad38e ("trace, AER: Move trace into unified interface")) that
exposes the problem, and I'm leaving on vacation before I can get this
into -next, have it smoke-tested, and ask Linus to pull it.
So you might want to ask Tony to put in his tree, since it looks like
he merged 0a2409aad38e in the first place.
Please add these:
Fixes: 0a2409aad38e ("trace, AER: Move trace into unified interface")
Acked-by: Bjorn Helgaas <bhelgaas@google.com>
I know 0a2409aad38e isn't actually *responsible* for the problem, but
anybody who backports 0a2409aad38e should pick up this fix as well.
Lance, I added you because of an unrelated issue I noticed while reviewing
this: you added the AER trace events with 1ca1d8d54f92 ("aerdrv: Trace
Event for PCI Express Advanced Error Reporting"):
+#define aer_correctable_errors \
+ {BIT(0), "Receiver Error"}, \
...
I'd like to see all those "BIT(...)" things changed to use the #defines
that already exist in include/uapi/linux/pci_regs.h, e.g.,
PCI_ERR_COR_RCVR. That way grep will find these uses, which will make
maintenance easier. There's no hurry about this part, of course.
Bjorn
> ---
> include/linux/aer.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/aer.h b/include/linux/aer.h
> index 4dbaa70..c826d1c 100644
> --- a/include/linux/aer.h
> +++ b/include/linux/aer.h
> @@ -11,6 +11,8 @@
> #define AER_FATAL 1
> #define AER_CORRECTABLE 2
>
> +struct pci_dev;
> +
> struct aer_header_log_regs {
> unsigned int dw0;
> unsigned int dw1;
> --
> 1.8.1.4
>
next prev parent reply other threads:[~2014-07-22 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 8:08 [PATCH] Fix build warnings in aer.h Mike Qiu
2014-07-16 18:08 ` Bjorn Helgaas
2014-07-22 1:59 ` Mike Qiu
2014-07-22 2:38 ` Bjorn Helgaas [this message]
2014-07-22 4:31 ` Randy Dunlap
2014-07-22 13:51 ` Bjorn Helgaas
2014-07-22 16:17 ` Luck, Tony
2014-07-22 4:51 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2014-07-29 17:49 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=20140722023813.GA27601@google.com \
--to=bhelgaas@google.com \
--cc=gong.chen@linux.intel.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=lance.ortiz@hp.com \
--cc=linux-pci@vger.kernel.org \
--cc=qiudayu@linux.vnet.ibm.com \
--cc=rdunlap@infradead.org \
--cc=tony.luck@intel.com \
--cc=ttynkkynen@nvidia.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).