# git rev-parse -q --verify b0d4beaa5a4b7d31070c41c2e50740304a3f1138^{commit}
b0d4beaa5a4b7d31070c41c2e50740304a3f1138
already have revision, skipping fetch
# git checkout -q -f -B kisskb b0d4beaa5a4b7d31070c41c2e50740304a3f1138
# git clean -qxdf
# < git log -1
# commit b0d4beaa5a4b7d31070c41c2e50740304a3f1138
# Merge: da73fcd8cfdc 850d71acd52c
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Thu Dec 5 17:11:48 2019 -0800
# 
#     Merge branch 'next.autofs' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs
#     
#     Pull autofs updates from Al Viro:
#      "autofs misuses checks for ->d_subdirs emptiness; the cursors are in
#       the same lists, resulting in false negatives. It's not needed anyway,
#       since autofs maintains counter in struct autofs_info, containing 0 for
#       removed ones, 1 for live symlinks and 1 + number of children for live
#       directories, which is precisely what we need for those checks.
#     
#       This series switches to use of that counter and untangles the crap
#       around its uses (it needs not be atomic and there's a bunch of
#       completely pointless "defensive" checks).
#     
#       This fell out of dcache_readdir work; the main point is to get rid of
#       ->d_subdirs abuses in there. I've more followup cleanups, but I hadn't
#       run those by Ian yet, so they can go next cycle"
#     
#     * 'next.autofs' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:
#       autofs: don't bother with atomics for ino->count
#       autofs_dir_rmdir(): check ino->count for deciding whether it's empty...
#       autofs: get rid of pointless checks around ->count handling
#       autofs_clear_leaf_automount_flags(): use ino->count instead of ->d_subdirs
# < /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 b0d4beaa5a4b7d31070c41c2e50740304a3f1138
# < make -s -j 24 ARCH=powerpc O=/kisskb/build/linus_pseries_le_defconfig+NO_SPLPAR_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  pseries_le_defconfig
# Added to kconfig CONFIG_PPC_SPLPAR=n
# yes \n | make -s -j 24 ARCH=powerpc O=/kisskb/build/linus_pseries_le_defconfig+NO_SPLPAR_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 24 ARCH=powerpc O=/kisskb/build/linus_pseries_le_defconfig+NO_SPLPAR_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  
WARNING: vmlinux.o(.text+0x2e1c): 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+0x2fc8): 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_pseries_le_defconfig+NO_SPLPAR_ppc64le-gcc5
# Build took: 0:03:22.360136