diff options
author | Masahiro Yamada <masahiroy@kernel.org> | 2020-03-02 15:23:40 +0900 |
---|---|---|
committer | Masahiro Yamada <masahiroy@kernel.org> | 2020-03-13 10:05:34 +0900 |
commit | 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d (patch) | |
tree | 7586526ac545db8fae708e3ad928b7a0789ea312 /Makefile | |
parent | def2fbffe62c00c330c7f41584a356001179c59c (diff) | |
download | linux-3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d.tar.bz2 |
kconfig: make 'imply' obey the direct dependency
The 'imply' statement may create unmet direct dependency when the
implied symbol depends on m.
[Test Code]
config FOO
tristate "foo"
imply BAZ
config BAZ
tristate "baz"
depends on BAR
config BAR
def_tristate m
config MODULES
def_bool y
option modules
If you set FOO=y, BAZ is also promoted to y, which results in the
following .config file:
CONFIG_FOO=y
CONFIG_BAZ=y
CONFIG_BAR=m
CONFIG_MODULES=y
This does not meet the dependency 'BAZ depends on BAR'.
Unlike 'select', what is worse, Kconfig never shows the
'WARNING: unmet direct dependencies detected for ...' for this case.
Because 'imply' is considered to be weaker than 'depends on', Kconfig
should take the direct dependency into account.
For clarification, describe this case in kconfig-language.rst too.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Acked-by: Nicolas Pitre <nico@fluxnic.net>
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions