# git rev-parse -q --verify 8f744bdee4fefb17fac052c7418b830de2b59ac8^{commit}
8f744bdee4fefb17fac052c7418b830de2b59ac8
already have revision, skipping fetch
# git checkout -q -f -B kisskb 8f744bdee4fefb17fac052c7418b830de2b59ac8
# git clean -qxdf
# < git log -1
# commit 8f744bdee4fefb17fac052c7418b830de2b59ac8
# Merge: 9977b1a71488 a62a8ef9d97d
# Author: Linus Torvalds <torvalds@linux-foundation.org>
# Date:   Fri Sep 27 15:54:24 2019 -0700
# 
#     Merge tag 'virtio-fs-5.4' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse
#     
#     Pull fuse virtio-fs support from Miklos Szeredi:
#      "Virtio-fs allows exporting directory trees on the host and mounting
#       them in guest(s).
#     
#       This isn't actually a new filesystem, but a glue layer between the
#       fuse filesystem and a virtio based back-end.
#     
#       It's similar in functionality to the existing virtio-9p solution, but
#       significantly faster in benchmarks and has better POSIX compliance.
#       Further permformance improvements can be achieved by sharing the page
#       cache between host and guest, allowing for faster I/O and reduced
#       memory use.
#     
#       Kata Containers have been including the out-of-tree virtio-fs (with
#       the shared page cache patches as well) since version 1.7 as an
#       experimental feature. They have been active in development and plan to
#       switch from virtio-9p to virtio-fs as their default solution. There
#       has been interest from other sources as well.
#     
#       The userspace infrastructure is slated to be merged into qemu once the
#       kernel part hits mainline.
#     
#       This was developed by Vivek Goyal, Dave Gilbert and Stefan Hajnoczi"
#     
#     * tag 'virtio-fs-5.4' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse:
#       virtio-fs: add virtiofs filesystem
#       virtio-fs: add Documentation/filesystems/virtiofs.rst
#       fuse: reserve values for mapping protocol
# < /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 8f744bdee4fefb17fac052c7418b830de2b59ac8
# < make -s -j 48 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 48 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-  
In file included from /kisskb/src/include/linux/list.h:9:0,
                 from /kisskb/src/include/linux/wait.h:7,
                 from /kisskb/src/include/linux/wait_bit.h:8,
                 from /kisskb/src/include/linux/fs.h:6,
                 from /kisskb/src/fs/btrfs/send.c:7:
/kisskb/src/fs/btrfs/send.c: In function 'process_extent':
/kisskb/src/include/linux/kernel.h:37:33: warning: 'clone_src_i_size' may be used uninitialized in this function [-Wmaybe-uninitialized]
 #define IS_ALIGNED(x, a)  (((x) & ((typeof(x))(a) - 1)) == 0)
                                 ^
/kisskb/src/fs/btrfs/send.c:5088:6: note: 'clone_src_i_size' was declared here
  u64 clone_src_i_size;
      ^
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:42.935045