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

From: Ingo Molnar
Date: Mon May 30 2011 - 06:47:08 EST



* Ingo Molnar <mingo@xxxxxxx> wrote:

> > I believe that this 'filtered randconfig' behaviour is now fairly
> > much the *only* use for the old 'ARCH=i386' and 'ARCH=x86_64'.
>
> Not really, there's also:
>
> make ARCH=i386 defconfig # writes 32-bit defconfig into .config
> make ARCH=x86_64 defconfig # writes 64-bit defconfig into .config
>
> make ARCH=i386 oldconfig # turns 64-bit .config int 32-bit equivalent
> make ARCH=x86_64 oldconfig # turns 32-bit .config int 64-bit equivalent
>
> And i use these variants myself, both as commands typed and in
> scripts, in addition to the randconfig variants:
>
> make ARCH=i386 randconfig # write 32-bit randconfig into .config
> make ARCH=x86_64 randconfig # write 64-bit randconfig into .config
>
> I'm pretty sure others are relying on these variants as well - they
> are fairly logical along several dimensions.

Not to mention all the other *config variants, which work in a
similar fashion:

make ARCH=i386 allnoconfig # writes 32-bit all-disabled config into .config
make ARCH=i386 allyesconfig # writes 32-bit all-enabled config into .config
make ARCH=i386 allmodconfig # writes 32-bit all-modules config into .config

make ARCH=x86_64 allnoconfig # writes 64-bit all-disabled config into .config
make ARCH=x86_64 allyesconfig # writes 64-bit all-enabled config into .config
make ARCH=x86_64 allmodconfig # writes 64-bit all-modules config into .config

and i use them in this fashion both as typed commands and in scripts,
and many other kernel developers are using them as well.

So contrary to your claim there's *one dozen* very useful uses of
this 'old' form - with no functional replacement AFAICS.

Thanks,

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