# git rev-parse -q --verify 357d065a44cdd77ed5ff35155a989f2a763e96ef^{commit}
357d065a44cdd77ed5ff35155a989f2a763e96ef
already have revision, skipping fetch
# git checkout -q -f -B kisskb 357d065a44cdd77ed5ff35155a989f2a763e96ef
# git clean -qxdf
# < git log -1
# commit 357d065a44cdd77ed5ff35155a989f2a763e96ef
# Author: Daniel Axtens <dja@axtens.net>
# Date:   Fri May 17 01:40:02 2019 +1000
# 
#     crypto: vmx - ghash: do nosimd fallback manually
#     
#     VMX ghash was using a fallback that did not support interleaving simd
#     and nosimd operations, leading to failures in the extended test suite.
#     
#     If I understood correctly, Eric's suggestion was to use the same
#     data format that the generic code uses, allowing us to call into it
#     with the same contexts. I wasn't able to get that to work - I think
#     there's a very different key structure and data layout being used.
#     
#     So instead steal the arm64 approach and perform the fallback
#     operations directly if required.
#     
#     Fixes: cc333cd68dfa ("crypto: vmx - Adding GHASH routines for VMX module")
#     Cc: stable@vger.kernel.org # v4.1+
#     Reported-by: Eric Biggers <ebiggers@google.com>
#     Signed-off-by: Daniel Axtens <dja@axtens.net>
#     Acked-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
#     Tested-by: Michael Ellerman <mpe@ellerman.id.au>
#     Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
# < /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 357d065a44cdd77ed5ff35155a989f2a763e96ef
# < make -s -j 40 ARCH=powerpc O=/kisskb/build/crypto_powernv_defconfig_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  powernv_defconfig
# make -s -j 40 ARCH=powerpc O=/kisskb/build/crypto_powernv_defconfig_ppc64le-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux-  
<stdin>:1478:2: warning: #warning syscall pidfd_send_signal not implemented [-Wcpp]
<stdin>:1481:2: warning: #warning syscall io_uring_setup not implemented [-Wcpp]
<stdin>:1484:2: warning: #warning syscall io_uring_enter not implemented [-Wcpp]
<stdin>:1487:2: warning: #warning syscall io_uring_register not implemented [-Wcpp]
/kisskb/src/net/sunrpc/xprtsock.c: In function 'xs_stream_data_receive':
/kisskb/src/net/sunrpc/xprtsock.c:529:9: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized]
  return ret < 0 ? ret : read;
         ^
/kisskb/src/net/sunrpc/xprtsock.c:499:10: note: 'ret' was declared here
  ssize_t ret;
          ^
/kisskb/src/net/sunrpc/xprtsock.c:498:15: warning: 'read' may be used uninitialized in this function [-Wmaybe-uninitialized]
  size_t want, read;
               ^
WARNING: vmlinux.o(.text+0x2d28): Section mismatch in reference from the variable start_here_multiplatform to the function .init.text:early_setup()
The function start_here_multiplatform() references
the function __init early_setup().
This is often because start_here_multiplatform lacks a __init 
annotation or the annotation of early_setup is wrong.

WARNING: vmlinux.o(.text+0x2d5c): 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/crypto_powernv_defconfig_ppc64le-gcc5
# Build took: 0:01:05.471912