# 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 # 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/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-gcc --version # < /opt/cross/kisskb/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-ld --version # < git log --format=%s --max-count=1 8f744bdee4fefb17fac052c7418b830de2b59ac8 # < make -s -j 48 ARCH=arm O=/kisskb/build/linus_assabet_defconfig_arm CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi- assabet_defconfig # make -s -j 48 ARCH=arm O=/kisskb/build/linus_assabet_defconfig_arm CROSS_COMPILE=/opt/cross/kisskb/gcc-4.6.3-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi- /kisskb/src/kernel/printk/printk.c: In function 'devkmsg_sysctl_set_loglvl': /kisskb/src/kernel/printk/printk.c:204:16: warning: 'old' may be used uninitialized in this function [-Wuninitialized] /kisskb/src/fs/proc/inode.c: In function 'proc_reg_open': /kisskb/src/include/linux/list.h:65:12: warning: 'pdeo' may be used uninitialized in this function [-Wuninitialized] /kisskb/src/fs/proc/inode.c:338:21: note: 'pdeo' was declared here /kisskb/src/drivers/video/fbdev/sa1100fb.c:975:21: warning: 'sa1100fb_min_dma_period' defined but not used [-Wunused-function] WARNING: vmlinux.o(.text.unlikely+0x75c): Section mismatch in reference from the function free_memmap() to the function .meminit.text:memblock_free() The function free_memmap() references the function __meminit memblock_free(). This is often because free_memmap lacks a __meminit annotation or the annotation of memblock_free is wrong. Completed OK # rm -rf /kisskb/build/linus_assabet_defconfig_arm # Build took: 0:00:34.091040