public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Michal Marek <mmarek@suse.cz>,
	JBeulich@novell.com, aris@redhat.com, catalin.marinas@arm.com,
	jacmet@sunsite.dk, lizf@cn.fujitsu.com, sam@ravnborg.org,
	ulfalizer.lkml@gmail.com, zippel@linux-m68k.org,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT] kbuild: kconfig changes
Date: Thu, 05 Aug 2010 19:54:32 -0700	[thread overview]
Message-ID: <4C5B7968.7070303@gmail.com> (raw)
In-Reply-To: <AANLkTikpsvpHuB-mWVfmqTRRMvbvhJz2LmoYBgtn4NQE@mail.gmail.com>

On 08/05/2010 07:08 PM, Linus Torvalds wrote:
> On Thu, Aug 5, 2010 at 6:27 PM, Justin P. Mattock
> <justinmattock@gmail.com>  wrote:
>>
>> With what I submitted I did not test make oldconfig, only make menuconfig
>> due to gcc 4.6.0 giving me a slew of warnings.
>>  From looking at make oldconfig I do see a more detailed explanation of what
>> each option is(last I remember it was more of a line with y/n)but then again
>> you could be seeing something completly different.
>
> Just test what I described:  do a "make oldconfig" (do it twice, if
> the first one needs to actually get some input). Do it on 2.6.35, and
> then on the current tree. Look at the _huge_ difference in output.
>

yeah I see what your hitting, just experienced what you posted

	make oldconfig
    scripts/kconfig/conf -o arch/x86/Kconfig
    #
    # configuration written to .config
    #

(just sits there)

seemed to not want to go away.(doing a make menuconfig got
make oldconfig to wake up of whatever it was in) as for reproducing
(even though already bisected) seems once make oldconfig starts working 
properly, hitting the above doesn't happen as easily.


>> Now if this is with what I submitted then I'll have a look at it and see if I can get this fixed.
>
> I just did a quick git bisect. It's introduced by commit 4062f1a4c030
> ("kconfig: use long options in conf") by Sam Ravnborg. Apparently that
> thing is totally buggy, and doesn't just change the option names, but
> actively breaks them.
>
>                   Linus
>

cool..

Justin P. Mattock

  reply	other threads:[~2010-08-06  2:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 12:51 [GIT] kbuild: kconfig changes Michal Marek
2010-08-05 23:33 ` Linus Torvalds
2010-08-06  1:27   ` Justin P. Mattock
2010-08-06  2:08     ` Linus Torvalds
2010-08-06  2:54       ` Justin P. Mattock [this message]
2010-08-06  5:13       ` [PATCH] kconfig: fix make oldconfig Sam Ravnborg
2010-08-06  6:02         ` Justin P. Mattock
2010-08-06 10:21         ` Michal Marek
2010-08-06 16:19           ` Linus Torvalds
2010-08-06 17:52             ` Sam Ravnborg
2010-08-06 18:09               ` Linus Torvalds
2010-08-06 19:52                 ` Justin P. Mattock
2010-08-06 23:19 ` [GIT] kbuild: kconfig changes Arve Hjønnevåg
2010-08-07  4:01   ` Sam Ravnborg
2010-08-07  4:43     ` Arve Hjønnevåg
2010-08-08 15:57       ` Sam Ravnborg
2010-08-10 14:04         ` Michal Marek
2010-08-10 14:25           ` Sam Ravnborg
2010-08-11 19:51       ` Sam Ravnborg
2010-08-11 20:34         ` Sam Ravnborg
2010-08-11 23:39           ` Arve Hjønnevåg
2010-08-12  3:45             ` 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=4C5B7968.7070303@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=JBeulich@novell.com \
    --cc=aris@redhat.com \
    --cc=catalin.marinas@arm.com \
    --cc=jacmet@sunsite.dk \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.org \
    --cc=torvalds@linux-foundation.org \
    --cc=ulfalizer.lkml@gmail.com \
    --cc=zippel@linux-m68k.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