From: Kevin Winchester <kwin@ns.sympatico.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: Compile Warnings on 2.6.16-rc5-mm1
Date: Thu, 02 Mar 2006 21:16:42 -0400 [thread overview]
Message-ID: <440798FA.4080306@ns.sympatico.ca> (raw)
In-Reply-To: <44078075.7000504@ns.sympatico.ca>
Kevin Winchester wrote:
>
> I get the following compile warnings on 2.6.16-rc5-mm1. I am looking
> into them, but someone probably knows why they're there right off.
>
> In file included from include/asm/hw_irq.h:23,
> from include/linux/irq.h:94,
> from include/asm/hardirq.h:6,
> from include/linux/hardirq.h:7,
> from include/linux/interrupt.h:11,
> from include/linux/rtc.h:14,
> from drivers/rtc/interface.c:14:
> include/linux/profile.h:66: warning: "struct notifier_block" declared
> inside parameter list
> include/linux/profile.h:66: warning: its scope is only this definition
> or declaration, which is probably not what you want
> include/linux/profile.h:71: warning: "struct notifier_block" declared
> inside parameter list
> include/linux/profile.h:76: warning: "struct notifier_block" declared
> inside parameter list
> include/linux/profile.h:81: warning: "struct notifier_block" declared
> inside parameter list
>
>
> These come up in lots and lots of files. Everything that includes
> hardirq.h it seems. My config is below.
>
<snip config>
I discovered I can make these go away by enabling CONFIG_PROFILING,
which was a wild guess since the problem happened in profile.h.
Kevin
prev parent reply other threads:[~2006-03-03 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 23:32 Compile Warnings on 2.6.16-rc5-mm1 Kevin Winchester
2006-03-03 1:16 ` Kevin Winchester [this message]
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=440798FA.4080306@ns.sympatico.ca \
--to=kwin@ns.sympatico.ca \
--cc=linux-kernel@vger.kernel.org \
/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