# git rev-parse -q --verify dd469a456047af5eb1ee0bcfc8fe61f5940ef0e0^{commit}
dd469a456047af5eb1ee0bcfc8fe61f5940ef0e0
already have revision, skipping fetch
# git checkout -q -f -B kisskb dd469a456047af5eb1ee0bcfc8fe61f5940ef0e0
# git clean -qxdf
# < git log -1
# commit dd469a456047af5eb1ee0bcfc8fe61f5940ef0e0
# Merge: f576518c9ab5 1cfd5d3399e8
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Fri Aug 23 10:53:34 2019 -0700
# 
#     Merge tag 'for-5.3/dm-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm
#     
#     Pull device mapper fixes from Mike Snitzer:
#     
#      - Revert a DM bufio change from during the 5.3 merge window now that a
#        proper fix has been made to the block loopback driver.
#     
#      - Fix DM kcopyd to wakeup so failed subjobs get completed.
#     
#      - Various fixes to DM zoned target to address error handling, and other
#        small tweaks (SPDX license identifiers and fix typos).
#     
#      - Fix DM integrity range locking race by tracking whether journal has
#        changed.
#     
#      - Fix DM dust target to detect reads of badblocks beyond the first 512b
#        sector (applicable if blocksize is larger than 512b).
#     
#      - Fix DM persistent-data issue in both the DM btree and DM
#        space-map-metadata interfaces.
#     
#      - Fix out of bounds memory access with certain DM table configurations.
#     
#     * tag 'for-5.3/dm-fixes-2' of git://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm:
#       dm table: fix invalid memory accesses with too high sector number
#       dm space map metadata: fix missing store of apply_bops() return value
#       dm btree: fix order of block initialization in btree_split_beneath
#       dm raid: add missing cleanup in raid_ctr()
#       dm zoned: fix potential NULL dereference in dmz_do_reclaim()
#       dm dust: use dust block size for badblocklist index
#       dm integrity: fix a crash due to BUG_ON in __journal_read_write()
#       dm zoned: fix a few typos
#       dm zoned: add SPDX license identifiers
#       dm zoned: properly handle backing device failure
#       dm zoned: improve error handling in i/o map code
#       dm zoned: improve error handling in reclaim
#       dm kcopyd: always complete failed jobs
#       Revert "dm bufio: fix deadlock with loop device"
# < /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 dd469a456047af5eb1ee0bcfc8fe61f5940ef0e0
# < make -s -j 120 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig+NO_KVM_ppc64le-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
# yes \n | make -s -j 120 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig+NO_KVM_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  oldconfig
yes: standard output: Broken pipe
# make -s -j 120 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig+NO_KVM_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  
/kisskb/src/kernel/futex.c: In function 'do_futex':
/kisskb/src/kernel/futex.c:1676:17: warning: 'oldval' may be used uninitialized in this function [-Wmaybe-uninitialized]
   return oldval == cmparg;
                 ^
/kisskb/src/kernel/futex.c:1651:6: note: 'oldval' was declared here
  int oldval, ret;
      ^
WARNING: vmlinux.o(.text+0x31f4): Section mismatch in reference from the variable __boot_from_prom to the function .init.text:prom_init()
The function __boot_from_prom() references
the function __init prom_init().
This is often because __boot_from_prom lacks a __init 
annotation or the annotation of prom_init is wrong.

WARNING: vmlinux.o(.text+0x33d0): Section mismatch in reference from the variable start_here_common to the function .init.text:start_kernel()
The function start_here_common() references
the function __init start_kernel().
This is often because start_here_common lacks a __init 
annotation or the annotation of start_kernel is wrong.

Completed OK
# rm -rf /kisskb/build/linus_ppc64le_defconfig+NO_KVM_ppc64le-gcc5
# Build took: 0:01:38.708240