Buildresult: linus/um-defconfig/um-x86_64 built on May 17 2018, 12:33

kisskb

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

Status:	OK
Date/Time:	May 17 2018, 12:33
Duration:	0:00:52.486962
Builder:	ka4
Revision:	Merge tag 'trace-v4.17-rc4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace (`e6506eb241871d68647c53cb6d0a16299550ae97)`
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 (1) arch/um/os-Linux/skas/process.c:613:1: warning: control reaches end of non-void function [-Wreturn-type] Full Log # git rev-parse -q --verify e6506eb241871d68647c53cb6d0a16299550ae97^{commit} e6506eb241871d68647c53cb6d0a16299550ae97 already have revision, skipping fetch # git checkout -q -f -B kisskb e6506eb241871d68647c53cb6d0a16299550ae97 # git clean -qxdf # < git log -1 # commit e6506eb241871d68647c53cb6d0a16299550ae97 # Merge: 9d38cd0 45dd9b0 # Author: Linus Torvalds <torvalds@linux-foundation.org> # Date: Wed May 16 16:45:23 2018 -0700 # # Merge tag 'trace-v4.17-rc4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace # # Pull tracing fix from Steven Rostedt: # "Some of the ftrace internal events use a zero for a data size of a # field event. This is increasingly important for the histogram trigger # work that is being extended. # # While auditing trace events, I found that a couple of the xen events # were used as just marking that a function was called, by creating a # static array of size zero. This can play havoc with the tracing # features if these events are used, because a zero size of a static # array is denoted as a special nul terminated dynamic array (this is # what the trace_marker code uses). But since the xen events have no # size, they are not nul terminated, and unexpected results may occur. # # As trace events were never intended on being a marker to denote that a # function was hit or not, especially since function tracing and kprobes # can trivially do the same, the best course of action is to simply # remove these events" # # * tag 'trace-v4.17-rc4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: # tracing/x86/xen: Remove zero data size trace events trace_xen_mmu_flush_tlb{_all} # < /opt/cross/kisskb/fe-x86-64-core-i7-2017.05/bin/x86_64-linux-gcc --version # < git log --format=%s --max-count=1 e6506eb241871d68647c53cb6d0a16299550ae97 # < make -s -j 10 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 10 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] } ^ LINK linux Completed OK # rm -rf /kisskb/build/linus_um-defconfig_um-x86_64 # Build took: 0:00:52.486962

© Michael Ellerman 2006-2018.