linux-kernel - Re: [PATCH] kbuild: fix oldnoconfig to do the right thing

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 09 Oct 2010 21:38:02 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	Kyle McMartin <kyle@...artin.ca>
Cc:	Sam Ravnborg <sam@...nborg.org>, linux-kbuild@...r.kernel.org,
	aris@...hat.com, linux-kernel@...r.kernel.org,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH] kbuild: fix oldnoconfig to do the right thing

On 8.10.2010 17:12, Kyle McMartin wrote:
> On Fri, Oct 08, 2010 at 04:54:38PM +0200, Michal Marek wrote:
>> 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.
>>
> 
> It's not a regression from .35, just trying to avoid unexpected changes

Yeah, I meant "bug introduced in 2.6.36-rc1".


> to how parts of the build system work after release (which means it
> could be perceived as a regression from .36 to .37)
> 
> IE: Someone begins to expect this behaviour in 2.6.36, and then
>  the patch goes into 2.6.37-rc1, so 2.6.37 behaves differently.

I see.

Michal
--
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/