public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Coywolf Qi Hunt <coywolf@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: rmk+lkml@arm.linux.org.uk, rmk+kernel@arm.linux.org.uk,
	sam@ravnborg.org, mm-commits@vger.kernel.org
Subject: Re: kbuild-permanently-fix-kernel-configuration-include-mess.patch added to -mm tree
Date: Wed, 14 Sep 2005 17:05:57 +0800	[thread overview]
Message-ID: <2cd57c900509140205572f19b7@mail.gmail.com> (raw)
In-Reply-To: <200509140841.j8E8fG1w022954@shell0.pdx.osdl.net>

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.
-- 
Coywolf Qi Hunt
http://sosdg.org/~coywolf/

       reply	other threads:[~2005-09-14  9:06 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 ` Coywolf Qi Hunt [this message]
2005-09-14  9:20   ` kbuild-permanently-fix-kernel-configuration-include-mess.patch added to -mm tree Russell King
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=2cd57c900509140205572f19b7@mail.gmail.com \
    --to=coywolf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    --cc=rmk+lkml@arm.linux.org.uk \
    --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