Re: Oddity with Kconfig behaviour when using a type definition andno prompt

[Michal Marek]

On 23.12.2010 20:38, David Peverley wrote:
> This is what I've always expected. Trying the following with a clean
> kernel. However, what happens in the (often used) case of a type definition
> with no prompt e.g.
>       bool
> is not defined in this doc. My _assumption_ would be that it should still
> be used by the config system though :
>
>    bob:linux-2.6.31.14 $ make defconfig
>    *** Default configuration is based on 'x86_64_defconfig'
>    #
>    # configuration written to .config
>    #
>    bob:linux-2.6.31.14 $ printf "\nconfig PEV_TEST\n\tbool\n">>  lib/Kconfig
>    bob:linux-2.6.31.14 $ make oldconfig
>    scripts/kconfig/conf -o arch/x86/Kconfig
>    #
>    # configuration written to .config
>    #


Symbols with no prompt are not prompted for, these can only be set if 
they have a default value or if some other symbol selects them.

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