All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Qiu <qiudayu@linux.vnet.ibm.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Tuomas Tynkkynen <ttynkkynen@nvidia.com>
Subject: Re: [PATCH] Fix build warnings in aer.h
Date: Tue, 22 Jul 2014 09:59:20 +0800	[thread overview]
Message-ID: <53CDC578.3090800@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAErSpo47WBkOuThU6ZW0htSm9s2P_r0ebZ6T3TM0dWiSdaGaBA@mail.gmail.com>

On 07/17/2014 02:08 AM, Bjorn Helgaas wrote:
> On Wed, Jul 16, 2014 at 2:08 AM, Mike Qiu <qiudayu@linux.vnet.ibm.com> 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>
> Hi Mike,
>
> How did you reproduce this build error?  There are other include files
> that use pci_dev without a previous declaration or include of
> include/linux/pci.h, e.g., include/linux/msi.h, so I want to make sure
> we don't have similar problems elsewhere.
( I have reply it before but seems haven't send out successful, just 
resend it, if you have seen, pls ignore this)
I checkout to linux-next master branch, see the top commit is:

commit b997a07604562f1a54cc531fe1cf7447f0ed6078
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date:   Tue Jul 15 18:34:28 2014 +1000

     Add linux-next specific files for 20140715

     Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>

Use default config file(copy from /boot/) then use command "make -j60",  
and it will show that message. but for "msi.h" I haven't see this warning.

Thanks,
Mike
> 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
>>


  reply	other threads:[~2014-07-22  1:59 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 [this message]
2014-07-22  2:38 ` Bjorn Helgaas
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=53CDC578.3090800@linux.vnet.ibm.com \
    --to=qiudayu@linux.vnet.ibm.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.