# git rev-parse -q --verify 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d^{commit}
3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d
already have revision, skipping fetch
# git checkout -q -f -B kisskb 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d
# git clean -qxdf
# < git log -1
# commit 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d
# Author: Masahiro Yamada <masahiroy@kernel.org>
# Date:   Mon Mar 2 15:23:40 2020 +0900
# 
#     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>
# < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-gcc --version
# < /opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-ld --version
# < git log --format=%s --max-count=1 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d
# < make -s -j 8 ARCH=powerpc O=/kisskb/build/kbuild_pseries_le_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  pseries_le_defconfig
# < make -s -j 8 ARCH=powerpc O=/kisskb/build/kbuild_pseries_le_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  help
# make -s -j 8 ARCH=powerpc O=/kisskb/build/kbuild_pseries_le_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  olddefconfig
# make -s -j 8 ARCH=powerpc O=/kisskb/build/kbuild_pseries_le_defconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  
WARNING: modpost: vmlinux.o(.text+0x31dc): Section mismatch in reference from the variable __boot_from_prom to the function .init.text:prom_init()
The function __boot_from_prom() references
the function __init prom_init().
This is often because __boot_from_prom lacks a __init 
annotation or the annotation of prom_init is wrong.

WARNING: modpost: vmlinux.o(.text+0x33c8): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel()
The function start_here_common() references
the function __init start_kernel().
This is often because start_here_common lacks a __init 
annotation or the annotation of start_kernel is wrong.

Completed OK
# rm -rf /kisskb/build/kbuild_pseries_le_defconfig_powerpc-gcc5
# Build took: 0:06:04.807729