# git rev-parse -q --verify f5ae2ea6347a308cfe91f53b53682ce635497d0d^{commit}
f5ae2ea6347a308cfe91f53b53682ce635497d0d
already have revision, skipping fetch
# git checkout -q -f -B kisskb f5ae2ea6347a308cfe91f53b53682ce635497d0d
# git clean -qxdf
# < git log -1
# commit f5ae2ea6347a308cfe91f53b53682ce635497d0d
# Author: Jari Ruusu <jari.ruusu@gmail.com>
# Date:   Sun Jan 12 15:00:53 2020 +0200
# 
#     Fix built-in early-load Intel microcode alignment
#     
#     Intel Software Developer's Manual, volume 3, chapter 9.11.6 says:
#     
#      "Note that the microcode update must be aligned on a 16-byte boundary
#       and the size of the microcode update must be 1-KByte granular"
#     
#     When early-load Intel microcode is loaded from initramfs, userspace tool
#     'iucode_tool' has already 16-byte aligned those microcode bits in that
#     initramfs image.  Image that was created something like this:
#     
#      iucode_tool --write-earlyfw=FOO.cpio microcode-files...
#     
#     However, when early-load Intel microcode is loaded from built-in
#     firmware BLOB using CONFIG_EXTRA_FIRMWARE= kernel config option, that
#     16-byte alignment is not guaranteed.
#     
#     Fix this by forcing all built-in firmware BLOBs to 16-byte alignment.
#     
#     [ If we end up having other firmware with much bigger alignment
#       requirements, we might need to introduce some method for the firmware
#       to specify it, this is the minimal "just increase the alignment a bit
#       to account for this one special case" patch    - Linus ]
#     
#     Signed-off-by: Jari Ruusu <jari.ruusu@gmail.com>
#     Cc: Borislav Petkov <bp@alien8.de>
#     Cc: Fenghua Yu <fenghua.yu@intel.com>
#     Cc: Luis Chamberlain <mcgrof@kernel.org>
#     Cc: stable@kernel.org
#     Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
# < /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 f5ae2ea6347a308cfe91f53b53682ce635497d0d
# < make -s -j 10 ARCH=powerpc O=/kisskb/build/linus_pseries_le_defconfig+NO_NUMA_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_NUMA=n
# yes \n | make -s -j 10 ARCH=powerpc O=/kisskb/build/linus_pseries_le_defconfig+NO_NUMA_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 10 ARCH=powerpc O=/kisskb/build/linus_pseries_le_defconfig+NO_NUMA_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  
WARNING: vmlinux.o(.text+0x31dc): 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_pseries_le_defconfig+NO_NUMA_ppc64le-gcc5
# Build took: 0:05:21.955614