From: Sam Ravnborg <sam@ravnborg.org>
To: Jaswinder Singh <jaswinderlinux@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.22.7 autoconf.h is screwed up
Date: Mon, 24 Sep 2007 13:57:49 +0200 [thread overview]
Message-ID: <20070924115749.GB3150@uranus.ravnborg.org> (raw)
In-Reply-To: <3f9a31f40709240320mb213a7an87cee8bf5517d7f7@mail.gmail.com>
On Mon, Sep 24, 2007 at 03:50:43PM +0530, Jaswinder Singh wrote:
> Hi all,
>
> 2.6.22.7's include/linux/autoconf.h is completely screwed up as
> compare to 2.6.10's autoconf.h .
>
> 2.6.22.7 totally changed the meaning of autoconf.h
autoconf.h has always been autogenerated. And autoconf.h has always
been used to publish the configuration to .c files.
What changed between 2.6.10 and 26.22 are the algorithm used to
produce autoconf.h.
The interface to the kernel configuration is .config - and overwriting
.config is an easy way to introduce a new config.
autoconf.h is not suitable for this purpose and thus
the actual layout does not matter.
If you used to use autoconf.h for distributing kernel versions before
I recommend you to use .config for now on. This should to my best
knowlege also work for your 2.6.10 kernel.
Sam
next prev parent reply other threads:[~2007-09-24 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 10:20 Jaswinder Singh
2007-09-24 10:26 ` Robert P. J. Day
2007-09-24 10:35 ` Jaswinder Singh
2007-09-24 10:37 ` Robert P. J. Day
2007-09-24 10:46 ` Jaswinder Singh
2007-09-24 10:49 ` Robert P. J. Day
2007-09-24 10:55 ` Jaswinder Singh
2007-09-25 7:10 ` Jan Engelhardt
2007-09-24 11:57 ` Sam Ravnborg [this message]
2007-09-24 12:06 ` Jaswinder Singh
2007-09-25 6:16 ` 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=20070924115749.GB3150@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jaswinderlinux@gmail.com \
--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
all inboxes | Powered by JetHome®