From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Dave Airlie <airlied@linux.ie>,
netdev@vger.kernel.org, linux-arm-kernel@lists.arm.linux.org.uk,
Herbert Xu <herbert@gondor.apana.org.au>,
Paul Moore <paul.moore@hp.com>, Takashi Iwai <tiwai@suse.de>,
Pekka Enberg <penberg@cs.helsinki.fi>,
xfs-masters@oss.sgi.com
Subject: Re: linux-next: arm allmodconfig
Date: Wed, 29 Oct 2008 09:05:49 -0700 [thread overview]
Message-ID: <20081029160547.GE20456@atomide.com> (raw)
In-Reply-To: <20081029094054.GA3796@flint.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [081029 02:59]:
> On Tue, Oct 28, 2008 at 05:56:04PM -0700, Andrew Morton wrote:
<snip>
>
> > > drivers/atm/ambassador.h:257:1: warning: "FLASH_BASE" redefined
> > > In file included from arch/arm/mach-versatile/include/mach/irqs.h:22,
> > > from /usr/src/devel/arch/arm/include/asm/irq.h:4,
> > > from /usr/src/devel/arch/arm/include/asm/hardirq.h:6,
> > > from include/linux/hardirq.h:7,
> > > from include/asm-generic/local.h:5,
> > > from /usr/src/devel/arch/arm/include/asm/local.h:1,
> > > from include/linux/module.h:20,
> > > from drivers/atm/ambassador.c:25:
> > > arch/arm/mach-versatile/include/mach/platform.h:443:1: warning: this is the location of the previous definition
> > > In file included from drivers/atm/ambassador.c:44:
> > > drivers/atm/ambassador.h:258:1: warning: "FLASH_SIZE" redefined
>
> Here we go again...
>
> I do wish that people wouldn't include "platform.h" headers defining lots
> of generically named constants into a header file used by most of the
> kernel build. It's stupid for several reasons:
>
> 1. see the above warnings.
> 2. if you change anything in that header, you're going to get a needless
> full kernel rebuild
> 3. and that causes additional strain on kautobuild's build caches
>
> We've had this in the past with sa1100-regs.h and similar, and we solved
> it there.
>
> Unfortunately, people persist in including their platform includes into
> lots of header files rather than having just the relevent C files include
> them. Eg, arch/arm/plat-omap/include/mach/hardware.h:
>
> /*
> * ---------------------------------------------------------------------------
> * Board specific defines
> * ---------------------------------------------------------------------------
> */
>
> #ifdef CONFIG_MACH_OMAP_INNOVATOR
> #include "board-innovator.h"
> #endif
>
> #ifdef CONFIG_MACH_OMAP_H2
> #include "board-h2.h"
> #endif
> ...
> #ifdef CONFIG_MACH_SX1
> #include "board-sx1.h"
> #endif
>
> which is included via asm/io.h, asm/irq.h, asm/pci.h, asm/vga.h.
>
> As long as this idiocracy, we're going to see these kinds of clashes.
> This stuff needs to die. I've a good idea to do a sweep of all ARM
> includes, and commit a patch to my devel tree for linux-next to remove
> such includes as an encouragement to fixing this stuff properly.
>
> People will then have a couple of months to sort out their mess.
I'll remove those omap includes, I have few other patches pending before
I get to that though.
Cheers,
Tony
next prev parent reply other threads:[~2008-10-29 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 0:56 linux-next: arm allmodconfig Andrew Morton
2008-10-29 7:12 ` Takashi Iwai
2008-10-29 7:40 ` [xfs-masters] " Dave Chinner
2008-10-29 8:24 ` Ingo Molnar
2008-10-29 22:07 ` [xfs-masters] " Dave Chinner
2008-10-29 9:40 ` Russell King - ARM Linux
2008-10-29 16:05 ` Tony Lindgren [this message]
2008-10-29 10:16 ` Pekka J Enberg
2008-10-29 13:53 ` Paul Moore
2008-10-29 20:12 ` Paul Moore
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=20081029160547.GE20456@atomide.com \
--to=tony@atomide.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=paul.moore@hp.com \
--cc=penberg@cs.helsinki.fi \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
--cc=xfs-masters@oss.sgi.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).