Buildresult: linus/mmu_defconfig/microblaze-gcc5 built on Jan 31 2019, 16:24

kisskb

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

Status:	OK
Date/Time:	Jan 31 2019, 16:24
Duration:	0:01:03.217740
Builder:	ka2
Revision:	fs/dcache: Track & report number of negative dentries (`af0c9af1b3f66052c369d08be3f60fa9a9559e48)`
Target:	linus/mmu_defconfig/microblaze-gcc5
Branch:	linus
Compiler:	microblaze-gcc5 (microblazeel-linux-gcc.br_real (Buildroot 2016.11-git-00613-ge98b4dd) 5.4.0 / GNU ld (GNU Binutils) 2.26.1)
Config:	mmu_defconfig (download)
Log:	Download original Possible warnings (1) drivers/i2c/i2c-core-base.c:235:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] Full Log # git rev-parse -q --verify af0c9af1b3f66052c369d08be3f60fa9a9559e48^{commit} af0c9af1b3f66052c369d08be3f60fa9a9559e48 already have revision, skipping fetch # git checkout -q -f -B kisskb af0c9af1b3f66052c369d08be3f60fa9a9559e48 # git clean -qxdf # < git log -1 # commit af0c9af1b3f66052c369d08be3f60fa9a9559e48 # Author: Waiman Long <longman@redhat.com> # Date: Wed Jan 30 13:52:38 2019 -0500 # # fs/dcache: Track & report number of negative dentries # # The current dentry number tracking code doesn't distinguish between # positive & negative dentries. It just reports the total number of # dentries in the LRU lists. # # As excessive number of negative dentries can have an impact on system # performance, it will be wise to track the number of positive and # negative dentries separately. # # This patch adds tracking for the total number of negative dentries in # the system LRU lists and reports it in the 5th field in the # /proc/sys/fs/dentry-state file. The number, however, does not include # negative dentries that are in flight but not in the LRU yet as well as # those in the shrinker lists which are on the way out anyway. # # The number of positive dentries in the LRU lists can be roughly found by # subtracting the number of negative dentries from the unused count. # # Matthew Wilcox had confirmed that since the introduction of the # dentry_stat structure in 2.1.60, the dummy array was there, probably for # future extension. They were not replacements of pre-existing fields. # So no sane applications that read the value of /proc/sys/fs/dentry-state # will do dummy thing if the last 2 fields of the sysctl parameter are not # zero. IOW, it will be safe to use one of the dummy array entry for # negative dentry count. # # Signed-off-by: Waiman Long <longman@redhat.com> # Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> # < /opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux-gcc --version # < /opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux-ld --version # < git log --format=%s --max-count=1 af0c9af1b3f66052c369d08be3f60fa9a9559e48 # < make -s -j 8 ARCH=microblaze O=/kisskb/build/linus_mmu_defconfig_microblaze CROSS_COMPILE=/opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux- mmu_defconfig # make -s -j 8 ARCH=microblaze O=/kisskb/build/linus_mmu_defconfig_microblaze CROSS_COMPILE=/opt/cross/kisskb/br-microblaze-full-2016.08-613-ge98b4dd/bin/microblazeel-linux- /kisskb/src/drivers/i2c/i2c-core-base.c: In function 'i2c_generic_scl_recovery': /kisskb/src/drivers/i2c/i2c-core-base.c:235:5: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized] if (ret == -EOPNOTSUPP) ^ Kernel: arch/microblaze/boot/linux.bin is ready (#1) Completed OK # rm -rf /kisskb/build/linus_mmu_defconfig_microblaze # Build took: 0:01:03.217740

© Michael Ellerman 2006-2018.