Re: [PATCH] Fix corruption of CONFIG_X86_32 in 'make oldconfig'

[Theodore Tso]

On May 30, 2011, at 6:58 AM, Ingo Molnar wrote:

> 
> * Theodore Tso <tytso@xxxxxxx> wrote:
> 
>> I'd think that "make ARCH=x86_64 oldconfig"
>> 
>> ... where the old configuration contained CONFIG_X86_32
>> should trigger a warning, if not an outright error that 
>> stops the build....
> 
> That would be a rather sad regression for me: i use that command 
> regularly to transform .configs that came in bugreports into a config 
> suitable for a testbox that has a different bitness userspace 
> installed.

OK, so to clarify, what you want is for ARCH=xxx to always override
whatever is in .config?  Are we all on the same page here?  I thought
David was arguing that what was in .config should always be more
important, since he regards "ARCH=xxxx" as "legacy".

Or maybe I'm missing something here.... since people seem to be slinging
around examples what should or should not work, as opposed to 
simply saying, "ARCH=xxx" must always override all else, even in 
cases like "oldconfig", "randconfig", etc.  Is that what the patch
is going to do?

All this talk of how it's OK for randconfig to give you i386 50% of the time
even when ARCH=x86_64 is specified is confusing me?  Maybe that
was just intended to be sarcasm?

-- Ted

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/