# 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/gcc-4.6.3-nolibc/s390x-linux/bin/s390x-linux-gcc --version
# < git log --format=%s --max-count=1 e6506eb241871d68647c53cb6d0a16299550ae97
# < make -s -j 10 ARCH=s390 O=/kisskb/build/linus_s390-defconfig_s390x CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/s390x-linux/bin/s390x-linux-  defconfig
# make -s -j 10 ARCH=s390 O=/kisskb/build/linus_s390-defconfig_s390x CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/s390x-linux/bin/s390x-linux-  
/kisskb/src/kernel/cgroup/cgroup-v1.c: In function 'cgroup1_mount':
/kisskb/src/kernel/cgroup/cgroup-v1.c:1268:20: warning: 'root' may be used uninitialized in this function [-Wuninitialized]
/kisskb/src/kernel/printk/printk.c: In function 'devkmsg_sysctl_set_loglvl':
/kisskb/src/kernel/printk/printk.c:183:16: warning: 'old' may be used uninitialized in this function [-Wuninitialized]
/kisskb/src/mm/hugetlb.c: In function 'alloc_pool_huge_page':
/kisskb/src/mm/hugetlb.c:1433:5: warning: 'page' may be used uninitialized in this function [-Wuninitialized]
/kisskb/src/fs/proc/inode.c: In function 'proc_reg_open':
/kisskb/src/include/linux/list.h:65:12: warning: 'pdeo' may be used uninitialized in this function [-Wuninitialized]
/kisskb/src/fs/proc/inode.c:340:21: note: 'pdeo' was declared here
/kisskb/src/drivers/net/tun.c: In function 'tun_get_user':
/kisskb/src/drivers/net/tun.c:1822:30: warning: 'copylen' may be used uninitialized in this function [-Wuninitialized]
/kisskb/src/drivers/net/tun.c:1732:46: warning: 'linear' may be used uninitialized in this function [-Wuninitialized]
Completed OK
# rm -rf /kisskb/build/linus_s390-defconfig_s390x
# Build took: 0:02:36.961814