# git rev-parse -q --verify d540c398db780271a81690eeb2bbc61876c37904^{commit}
d540c398db780271a81690eeb2bbc61876c37904
already have revision, skipping fetch
# git checkout -q -f -B kisskb d540c398db780271a81690eeb2bbc61876c37904
# git clean -qxdf
# < git log -1
# commit d540c398db780271a81690eeb2bbc61876c37904
# Merge: b88866b60d98 1cf45b8fdbb8
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Fri Nov 1 10:03:46 2019 -0700
# 
#     Merge tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
#     
#     Pull arm64 fixes from Will Deacon:
#      "These are almost exclusively related to CPU errata in CPUs from
#       Broadcom and Qualcomm where the workarounds were either not being
#       enabled when they should have been or enabled when they shouldn't have
#       been.
#     
#       The only "interesting" fix is ensuring that writeable, shared mappings
#       are initially mapped as clean since we inadvertently broke the logic
#       back in v4.14 and then noticed the problem via code inspection the
#       other day.
#     
#       The only critical issue we have outstanding is a sporadic NULL
#       dereference in the scheduler, which doesn't appear to be
#       arm64-specific and PeterZ is tearing his hair out over it at the
#       moment.
#     
#       Summary:
#     
#        - Enable CPU errata workarounds for Broadcom Brahma-B53
#     
#        - Enable CPU errata workarounds for Qualcomm Hydra/Kryo CPUs
#     
#        - Fix initial dirty status of writeable, shared mappings"
#     
#     * tag 'arm64-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux:
#       arm64: apply ARM64_ERRATUM_843419 workaround for Brahma-B53 core
#       arm64: Brahma-B53 is SSB and spectre v2 safe
#       arm64: apply ARM64_ERRATUM_845719 workaround for Brahma-B53 core
#       arm64: cpufeature: Enable Qualcomm Falkor errata 1009 for Kryo
#       arm64: cpufeature: Enable Qualcomm Falkor/Kryo errata 1003
#       arm64: Ensure VM_WRITE|VM_SHARED ptes are clean by default
# < /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 d540c398db780271a81690eeb2bbc61876c37904
# < make -s -j 80 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  ppc64le_defconfig
# make -s -j 80 ARCH=powerpc O=/kisskb/build/linus_ppc64le_defconfig_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  
WARNING: vmlinux.o(.text+0x31e4): 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+0x33c8): 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_ppc64le-gcc5
# Build took: 0:02:51.517319