From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Coywolf Qi Hunt <coywolf@gmail.com>
Cc: linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: kbuild-permanently-fix-kernel-configuration-include-mess.patch added to -mm tree
Date: Wed, 14 Sep 2005 10:20:16 +0100 [thread overview]
Message-ID: <20050914102016.B30672@flint.arm.linux.org.uk> (raw)
In-Reply-To: <2cd57c900509140205572f19b7@mail.gmail.com>; from coywolf@gmail.com on Wed, Sep 14, 2005 at 05:05:57PM +0800
On Wed, Sep 14, 2005 at 05:05:57PM +0800, Coywolf Qi Hunt wrote:
> On 9/14/05, akpm@osdl.org <akpm@osdl.org> wrote:
> >
> > The patch titled
> >
> > kbuild: permanently fix kernel configuration include mess.
> >
> > has been added to the -mm tree. Its filename is
> >
> > kbuild-permanently-fix-kernel-configuration-include-mess.patch
> >
> >
> > From: Russell King <rmk+lkml@arm.linux.org.uk>
> >
> > Include autoconf.h into every kernel compilation via the gcc command line
> > using -imacros. This ensures that we have the kernel configuration
> > included from the start, rather than relying on each file having #include
> > <linux/config.h> as appropriate. History has shown that this is something
> > which is difficult to get right.
>
> Not all compilations need config.h included and this slows down gratuitously.
That is a small price to pay, rather than having to continually maintain
"does this file need config.h included" - which I think can conclusively
be shown to be a total lost cause. There are about 3450 configuration
include errors in the kernel as of -git last night.
Getting config.h includes wrong causes subtle bugs - for instance, one
file may be built with some feature enabled which changes a structure
size, and another filfe may be built with it disabled.
I put forward that maintaining correct config.h include across all
files is demonstratably impossible in such a large source base without
considerable work.
I also put forward that the percentage of compilations which do not need
config.h is small and probably realistically zero.
Therefore, I think that a small slowdown for the few (if any) files which
don't need linux/config.h including is a good tradeoff.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-09-14 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200509140841.j8E8fG1w022954@shell0.pdx.osdl.net>
2005-09-14 9:05 ` kbuild-permanently-fix-kernel-configuration-include-mess.patch added to -mm tree Coywolf Qi Hunt
2005-09-14 9:20 ` Russell King [this message]
2005-09-14 10:58 ` Alan Cox
2005-09-14 17:26 ` Sam Ravnborg
2005-09-14 16:49 ` Sam Ravnborg
2005-09-14 16:53 ` Russell King
2005-09-14 16:58 ` Sam Ravnborg
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=20050914102016.B30672@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=coywolf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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