Buildresult: linus/um-defconfig/um-x86_64 built on Jun 12 2018, 04:01

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Jun 12 2018, 04:01
Duration:	0:00:24.181540
Builder:	ka4
Revision:	autofs: remove left-over autofs4 stubs (`a2225d931f75ddd3c39f4d0d195fad99dfd68671)`
Target:	linus/um-defconfig/um-x86_64
Branch:	linus
Compiler:	um-x86_64 (x86_64-linux-gcc.br_real (Buildroot 2017.05) 5.4.0)
Config:	defconfig (download)
Log:	Download original Possible warnings (2) arch/um/os-Linux/skas/process.c:613:1: warning: control reaches end of non-void function [-Wreturn-type] net/core/rtnetlink.c:3099:1: warning: the frame size of 1280 bytes is larger than 1024 bytes [-Wframe-larger-than=] Full Log # git rev-parse -q --verify a2225d931f75ddd3c39f4d0d195fad99dfd68671^{commit} a2225d931f75ddd3c39f4d0d195fad99dfd68671 already have revision, skipping fetch # git checkout -q -f -B kisskb a2225d931f75ddd3c39f4d0d195fad99dfd68671 # git clean -qxdf # < git log -1 # commit a2225d931f75ddd3c39f4d0d195fad99dfd68671 # Author: Linus Torvalds <torvalds@linux-foundation.org> # Date: Mon Jun 11 08:22:34 2018 -0700 # # autofs: remove left-over autofs4 stubs # # There's no need to retain the fs/autofs4 directory for backward # compatibility. # # Adding an AUTOFS4_FS fragment to the autofs Kconfig and a module alias # for autofs4 is sufficient for almost all cases. Not keeping fs/autofs4 # remnants will prevent "insmod <path>/autofs4/autofs4.ko" from working # but this shouldn't be used in automation scripts rather than # modprobe(8). # # There were some comments about things to look out for with the module # rename in the fs/autofs4/Kconfig that is removed by this patch, see the # commit patch if you are interested. # # One potential problem with this change is that when the # fs/autofs/Kconfig fragment for AUTOFS4_FS is removed any AUTOFS4_FS # entries will be removed from the kernel config, resulting in no autofs # file system being built if there is no AUTOFS_FS entry also. # # This would have also happened if the fs/autofs4 remnants had remained # and is most likely to be a problem with automated builds. # # Please check your build configurations before the removal which will # occur after the next couple of kernel releases. # # Acked-by: Ian Kent <raven@themaw.net> # [ With edits and commit message from Ian Kent ] # Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux-gcc --version # < git log --format=%s --max-count=1 a2225d931f75ddd3c39f4d0d195fad99dfd68671 # < make -s -j 120 ARCH=um O=/kisskb/build/linus_um-defconfig_um-x86_64 CROSS_COMPILE=/opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux- SUBARCH=x86_64 defconfig # make -s -j 120 ARCH=um O=/kisskb/build/linus_um-defconfig_um-x86_64 CROSS_COMPILE=/opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux- SUBARCH=x86_64 /kisskb/src/arch/um/os-Linux/skas/process.c: In function 'start_idle_thread': /kisskb/src/arch/um/os-Linux/skas/process.c:613:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ /kisskb/src/net/core/rtnetlink.c: In function 'rtnl_newlink': /kisskb/src/net/core/rtnetlink.c:3099:1: warning: the frame size of 1280 bytes is larger than 1024 bytes [-Wframe-larger-than=] } ^ LINK linux Completed OK # rm -rf /kisskb/build/linus_um-defconfig_um-x86_64 # Build took: 0:00:24.181540

© Michael Ellerman 2006-2018.