All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	linux-kbuild@vger.kernel.org, aris@redhat.com,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: [PATCH] kbuild: fix oldnoconfig to do the right thing
Date: Fri, 08 Oct 2010 16:54:38 +0200	[thread overview]
Message-ID: <4CAF30AE.3040305@suse.cz> (raw)
In-Reply-To: <20101008143642.GA24144@bombadil.infradead.org>

On 8.10.2010 16:36, Kyle McMartin wrote:
> On Wed, Sep 08, 2010 at 01:55:53PM +0200, Michal Marek wrote:
>> 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.
>>
> 
> Hi Michal,
> 
> Can we get this sent to Linus before 2.6.36? It would be awkward to
> release 2.6.36 with oldnoconfig working the broken way, and then patch
> it after release.

Oh, sorry, I didn't realize that this is a regression from 2.6.35 and
applied it to the kconfig branch, which is part of for-next. I'll try to
send a pull request with this patch and two other later today, but I
don't know if Linus is going to accept it.

Michal

  reply	other threads:[~2010-10-08 14:54 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
2010-09-08 13:01     ` Kyle McMartin
2010-10-08 14:36     ` Kyle McMartin
2010-10-08 14:54       ` Michal Marek [this message]
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=4CAF30AE.3040305@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 \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.