From: Michal Marek <mmarek@suse.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
linux-kbuild@vger.kernel.org, aris@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: fix oldnoconfig to do the right thing
Date: Wed, 8 Sep 2010 13:55:53 +0200 [thread overview]
Message-ID: <20100908115553.GC2617@sepie.suse.cz> (raw)
In-Reply-To: <20100905061758.GA29547@merkur.ravnborg.org>
On Sun, Sep 05, 2010 at 08:17:58AM +0200, Sam Ravnborg wrote:
> On Wed, Sep 01, 2010 at 11:21:30AM -0400, Kyle McMartin wrote:
> > From: Kyle McMartin <kyle@redhat.com>
> >
> > Commit 861b4ea4 broke oldnoconfig when removed the oldnoconfig checks on
> > if (input_mode == nonint_oldconfig ||
> > input_mode == oldnoconfig) {
> > if (input_mode == nonint_oldconfig &&
> > sym->name &&
> > !sym_is_choice_value(sym)) {
> > to avoid oldnoconfig chugging through the else stanza.
> >
> > Fix that to restore expected behaviour (which I've confirmed in the
> > Fedora kernel build that the configs end up looking the same.)
>
> I played aroud with this.
> I looks like the only difference I got was that before
> your patch oldnoconfig produced a lot of output to stdout.
> With your patch is was silent.
>
> The resulting config was the same.
I found that when running make oldnoconfig on the kconfig branch of
kbuild.git (which is currently a 2.6.35 + kconfig changes) against a
2.6.35-rc1 x86_64 defconfig, it mysteriously switches from
CONFIG_KERNEL_GZIP=y to CONFIG_KERNEL_LZO=y. With Kyle's patch it
doesn't do this. I applied the patch now.
Michal
next prev parent reply other threads:[~2010-09-08 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 15:21 [PATCH] kbuild: fix oldnoconfig to do the right thing Kyle McMartin
2010-09-05 6:17 ` Sam Ravnborg
2010-09-08 11:55 ` Michal Marek [this message]
2010-09-08 13:01 ` Kyle McMartin
2010-10-08 14:36 ` Kyle McMartin
2010-10-08 14:54 ` Michal Marek
2010-10-08 15:12 ` Kyle McMartin
2010-10-09 19:38 ` Michal Marek
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=20100908115553.GC2617@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=aris@redhat.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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