# git rev-parse -q --verify b9388959ba507c7a48ac18e4aa3b63b8a910ed99^{commit}
b9388959ba507c7a48ac18e4aa3b63b8a910ed99
already have revision, skipping fetch
# git checkout -q -f -B kisskb b9388959ba507c7a48ac18e4aa3b63b8a910ed99
# git clean -qxdf
# < git log -1
# commit b9388959ba507c7a48ac18e4aa3b63b8a910ed99
# Merge: 3c40cdb0e93e b31d1d2b1c3a
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Wed May 6 16:40:14 2020 -0700
# 
#     Merge tag 'tag-chrome-platform-fixes-for-v5.7-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux
#     
#     Pull chrome platform fix from Benson Leung:
#      "Fix a resource allocation issue in cros_ec_sensorhub.c"
#     
#     * tag 'tag-chrome-platform-fixes-for-v5.7-rc5' of git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux:
#       platform/chrome: cros_ec_sensorhub: Allocate sensorhub resource before claiming sensors
# < /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 b9388959ba507c7a48ac18e4aa3b63b8a910ed99
# < make -s -j 24 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig+NO_KVM_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  ppc64le_defconfig
# Added to kconfig CONFIG_KVM_BOOK3S_64=n
# Added to kconfig CONFIG_KVM=n
# < make -s -j 24 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig+NO_KVM_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  help
# make -s -j 24 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig+NO_KVM_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  olddefconfig
# make -s -j 24 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig+NO_KVM_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  
/kisskb/src/kernel/trace/ftrace.c: In function 'pid_open':
/kisskb/src/kernel/trace/ftrace.c:7167:6: warning: 'seq_ops' may be used uninitialized in this function [-Wmaybe-uninitialized]
  ret = seq_open(file, seq_ops);
      ^
/kisskb/src/kernel/trace/ftrace.c: In function 'pid_write':
/kisskb/src/kernel/trace/ftrace.c:7245:8: warning: 'filtered_pids' may be used uninitialized in this function [-Wmaybe-uninitialized]
  ret = trace_pid_write(filtered_pids, &pid_list, ubuf, cnt);
        ^
/kisskb/src/kernel/trace/ftrace.c:7262:22: warning: 'other_pids' may be used uninitialized in this function [-Wmaybe-uninitialized]
  } else if (pid_list && !other_pids) {
                      ^
WARNING: modpost: vmlinux.o(.text.unlikely+0x2b0): Section mismatch in reference from the function early_init_mmu() to the function .init.text:radix__early_init_mmu()
The function early_init_mmu() references
the function __init radix__early_init_mmu().
This is often because early_init_mmu lacks a __init 
annotation or the annotation of radix__early_init_mmu is wrong.

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

Completed OK
# rm -rf /kisskb/build/linus_ppc64le_defconfig+NO_KVM_powerpc-gcc5
# Build took: 0:03:39.102917