Buildresult: linus-rand/powerpc-randconfig/powerpc-gcc5 built on Jan 13 2019, 11:04

kisskb

Revisions | Branches | Compilers | Configs | Build Results | Build Failures |

Status:	OK
Date/Time:	Jan 13 2019, 11:04
Duration:	0:02:47.912273
Builder:	ka3
Revision:	Merge tag 'remove-dma_zalloc_coherent-5.0' of git://git.infradead.org/users/hch/dma-mapping (`66c56cfa64d9dbb9efa8a06c1aece77e8d57ea19)`
Target:	linus-rand/powerpc-randconfig/powerpc-gcc5
Branch:	linus-rand
Compiler:	powerpc-gcc5 (powerpc64-linux-gcc (GCC) 5.5.0 / GNU ld (GNU Binutils) 2.29.1.20170915)
Config:	randconfig (download)
Log:	Download original No warnings found in log. Full Log # git rev-parse -q --verify 66c56cfa64d9dbb9efa8a06c1aece77e8d57ea19^{commit} 66c56cfa64d9dbb9efa8a06c1aece77e8d57ea19 already have revision, skipping fetch # git checkout -q -f -B kisskb 66c56cfa64d9dbb9efa8a06c1aece77e8d57ea19 # git clean -qxdf # < git log -1 # commit 66c56cfa64d9dbb9efa8a06c1aece77e8d57ea19 # Merge: 473348891c36 dfd32cad146e # Author: Linus Torvalds <torvalds@linux-foundation.org> # Date: Sat Jan 12 10:52:40 2019 -0800 # # Merge tag 'remove-dma_zalloc_coherent-5.0' of git://git.infradead.org/users/hch/dma-mapping # # Pull dma_zalloc_coherent() removal from Christoph Hellwig: # "We've always had a weird situation around dma_zalloc_coherent. To # safely support mapping the allocations to userspace major # architectures like x86 and arm have always zeroed allocations from # dma_alloc_coherent, but a couple other architectures were missing that # zeroing either always or in corner cases. # # Then later we grew anothe dma_zalloc_coherent interface to explicitly # request zeroing, but that just added __GFP_ZERO to the allocation # flags, which for some allocators that didn't end up using the page # allocator ended up being a no-op and still not zeroing the # allocations. # # So for this merge window I fixed up all remaining architectures to # zero the memory in dma_alloc_coherent, and made dma_zalloc_coherent a # no-op wrapper around dma_alloc_coherent, which fixes all of the above # issues. # # dma_zalloc_coherent is now pointless and can go away, and Luis helped # me writing a cocchinelle script and patch series to kill it, which I # think we should apply now just after -rc1 to finally settle these # issue" # # * tag 'remove-dma_zalloc_coherent-5.0' of git://git.infradead.org/users/hch/dma-mapping: # dma-mapping: remove dma_zalloc_coherent() # cross-tree: phase out dma_zalloc_coherent() on headers # cross-tree: phase out dma_zalloc_coherent() # < /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 66c56cfa64d9dbb9efa8a06c1aece77e8d57ea19 # < make -s -j 80 ARCH=powerpc O=/kisskb/build/linus-rand_powerpc-randconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- randconfig KCONFIG_SEED=0x7B66F774 # Added to kconfig CONFIG_STANDALONE=y # Added to kconfig CONFIG_BUILD_DOCSRC=n # Added to kconfig CONFIG_MODULE_SIG=n # Added to kconfig CONFIG_CPU_BIG_ENDIAN=y # Added to kconfig CONFIG_PPC64=y # Added to kconfig CONFIG_PPC_DISABLE_WERROR=y # Added to kconfig CONFIG_SECTION_MISMATCH_WARN_ONLY=y # Added to kconfig CONFIG_PREVENT_FIRMWARE_BUILD=y # Added to kconfig CONFIG_CC_STACKPROTECTOR_STRONG=n # Added to kconfig CONFIG_GCC_PLUGINS=n # Added to kconfig CONFIG_LD_HEAD_STUB_CATCH=y # Added to kconfig # yes \n \| make -s -j 80 ARCH=powerpc O=/kisskb/build/linus-rand_powerpc-randconfig_powerpc-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 80 ARCH=powerpc O=/kisskb/build/linus-rand_powerpc-randconfig_powerpc-gcc5 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-5.5.0-nolibc/powerpc64-linux/bin/powerpc64-linux- Completed OK # rm -rf /kisskb/build/linus-rand_powerpc-randconfig_powerpc-gcc5 # Build took: 0:02:47.912273

© Michael Ellerman 2006-2018.