From: "Jaswinder Singh" <jaswinderlinux@gmail.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.22.7 autoconf.h is screwed up
Date: Mon, 24 Sep 2007 16:05:25 +0530 [thread overview]
Message-ID: <3f9a31f40709240335w441699b5y366211baeebde871@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709240625140.31104@localhost.localdomain>
hello rday,
In my view autoconf.h is the index of kernel you are using. By reading
autoconf.h you will know what Architecture, drivers is selected.
For example, If we are using some ARM based board, If you give me your
autoconf.h , I can replicate same environment as yours. If it is not
properly formatted it is very difficult to read and come to some
conclusion.
Thank you,
Jaswinder Singh.
On 9/24/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> On Mon, 24 Sep 2007, 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
> ... snip ...
>
> why do you care what autoconf.h looks like? it's automatically
> generated, it's not something you should be messing with.
>
> rday
>
> --
> ========================================================================
> Robert P. J. Day
> Linux Consulting, Training and Annoying Kernel Pedantry
> Waterloo, Ontario, CANADA
>
> http://crashcourse.ca
> ========================================================================
>
next prev parent reply other threads:[~2007-09-24 10:35 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 [this message]
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
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=3f9a31f40709240335w441699b5y366211baeebde871@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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
all inboxes | Powered by JetHome®