# git rev-parse -q --verify 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d^{commit} # git fetch -q -n -f git://gitlab.ozlabs.ibm.com/mirror/linux-kbuild.git for-next # git rev-parse -q --verify 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d^{commit} 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d # git checkout -q -f -B kisskb 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d # git clean -qxdf # < git log -1 # commit 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d # Author: Masahiro Yamada # 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 # Acked-by: Nicolas Pitre # Tested-by: Geert Uytterhoeven # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-gcc --version # < /opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux-ld --version # < git log --format=%s --max-count=1 3a9dd3ecb207b2cb8a4aabd12d20e43fa360b66d # < make -s -j 10 ARCH=arm64 O=/kisskb/build/kbuild_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- defconfig # < make -s -j 10 ARCH=arm64 O=/kisskb/build/kbuild_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- help # make -s -j 10 ARCH=arm64 O=/kisskb/build/kbuild_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- olddefconfig # make -s -j 10 ARCH=arm64 O=/kisskb/build/kbuild_arm64-defconfig_arm64-gcc5.4 CROSS_COMPILE=/opt/cross/kisskb/br-aarch64-glibc-2016.08-613-ge98b4dd/bin/aarch64-linux- arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum arch/arm64/Makefile:35: LSE atomics not supported by binutils In file included from /kisskb/src/include/linux/rwsem.h:16:0, from /kisskb/src/include/linux/notifier.h:15, from /kisskb/src/include/linux/clk.h:14, from /kisskb/src/drivers/tty/serial/sh-sci.c:20: /kisskb/src/drivers/tty/serial/sh-sci.c: In function 'sci_dma_rx_submit': /kisskb/src/include/linux/spinlock.h:288:3: warning: 'flags' may be used uninitialized in this function [-Wmaybe-uninitialized] _raw_spin_unlock_irqrestore(lock, flags); \ ^ /kisskb/src/drivers/tty/serial/sh-sci.c:1348:16: note: 'flags' was declared here unsigned long flags; ^ /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c: In function 'sh_mobile_i2c_isr': /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c:399:26: warning: 'data' may be used uninitialized in this function [-Wmaybe-uninitialized] pd->msg->buf[real_pos] = data; ^ /kisskb/src/drivers/i2c/busses/i2c-sh_mobile.c:372:16: note: 'data' was declared here unsigned char data; ^ Completed OK # rm -rf /kisskb/build/kbuild_arm64-defconfig_arm64-gcc5.4 # Build took: 0:10:21.091219