linux-kernel - Re: 2.6.22.7 autoconf.h is screwed up

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3f9a31f40709240335w441699b5y366211baeebde871@mail.gmail.com>
Date:	Mon, 24 Sep 2007 16:05:25 +0530
From:	"Jaswinder Singh" <jaswinderlinux@...il.com>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.22.7 autoconf.h is screwed up

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@...dspring.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
> ========================================================================
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/