FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git
topic/renesas-overlays
commit 3edd9bd9184acaac993d58b8177e176ea073c4a5 ("kbuild: Enable DT symbols when
CONFIG_OF_OVERLAY is used")
As below, the log "### dt-test ### FAIL of_unittest_parse_phandle_with_args():300
of_count_phandle_with_args() returned -22, expected 7" showed with your commit.
[ 5.690908] Loading compiled-in X.509 certificates
[ 5.691622] page_owner is disabled
[ 5.693067] cryptomgr_probe (153) used greatest stack depth: 13960 bytes left
[ 5.693955] Key type trusted registered
[ 5.694911] Key type encrypted registered
[ 5.700168] device-tree: Duplicate name in testcase-data, renamed to
"duplicate-name#1"
[ 5.708499] ### dt-test ### start of unittest - you will see error messages
[ 5.709689] /testcase-data/phandle-tests/consumer-a: could not find phandle
[ 5.710491] ### dt-test ### FAIL of_unittest_parse_phandle_with_args():300
of_count_phandle_with_args() returned -22, expected 7
[ 5.711882] ### dt-test ### FAIL of_unittest_parse_phandle_with_args():354 index 0 -
data error on node /testcase-data/phandle-tests/provider2 rc=0
[ 5.713345] ### dt-test ### FAIL of_unittest_parse_phandle_with_args():354 index 1 -
data error on node /testcase-data/phandle-tests/provider1 rc=0
[ 5.714764] ### dt-test ### FAIL of_unittest_parse_phandle_with_args():354 index 3 -
data error on node /testcase-data/phandle-tests/provider0 rc=0
[ 5.716283] ### dt-test ### FAIL of_unittest_parse_phandle_with_args():354 index 4 -
data error on node /testcase-data/phandle-tests/provider3 rc=0
[ 5.717772] /testcase-data/phandle-tests/consumer-a: could not find phandle
[ 5.718578] ### dt-test ### FAIL of_unittest_parse_phandle_with_args():354 index 6 -
data error on node /testcase-data/phandle-tests/provider0 rc=-22
[ 5.720108] /testcase-data/phandle-tests/consumer-a: could not find phandle
[ 5.720963] ### dt-test ### FAIL of_unittest_parse_phandle_with_args():354 index 7 -
data error on node /testcase-data/phandle-tests/provider0 rc=-22
[ 5.722424] /testcase-data/phandle-tests/consumer-a: could not get
#phandle-cells-missing for /testcase-data/phandle-tests/provider2
[ 5.723742] /testcase-data/phandle-tests/consumer-a: could not get
#phandle-cells-missing for /testcase-data/phandle-tests/provider2
[ 5.725054] /testcase-data/phandle-tests/consumer-a: could not find phandle
[ 5.725816] /testcase-data/phandle-tests/consumer-a: could not find phandle
[ 5.726585] ### dt-test ### FAIL of_unittest_parse_phandle_with_args():384 expected:-22
got:-2
[ 5.727594] ### dt-test ### FAIL of_unittest_parse_phandle_with_args():387 expected:-22
got:2
[ 5.728970]
FYI, raw QEMU command line is:
qemu-system-x86_64 -enable-kvm -cpu Nehalem -kernel
/pkg/linux/x86_64-randconfig-s2-03292311/gcc-5/3edd9bd9184acaac993d58b8177e176ea073c4a5/vmlinuz-4.6.0-rc1-00030-g3edd9bd
-append 'root=/dev/ram0 user=lkp
job=/lkp/scheduled/vm-intel12-yocto-x86_64-9/bisect_boot-1-yocto-minimal-x86_64.cgz-x86_64-randconfig-s2-03292311-3edd9bd9184acaac993d58b8177e176ea073c4a5-20160330-40309-1w14x1w-0.yaml
ARCH=x86_64 kconfig=x86_64-randconfig-s2-03292311
branch=linux-devel/devel-spot-201603292222 commit=3edd9bd9184acaac993d58b8177e176ea073c4a5
BOOT_IMAGE=/pkg/linux/x86_64-randconfig-s2-03292311/gcc-5/3edd9bd9184acaac993d58b8177e176ea073c4a5/vmlinuz-4.6.0-rc1-00030-g3edd9bd
max_uptime=600
RESULT_ROOT=/result/boot/1/vm-intel12-yocto-x86_64/yocto-minimal-x86_64.cgz/x86_64-randconfig-s2-03292311/gcc-5/3edd9bd9184acaac993d58b8177e176ea073c4a5/0
LKP_SERVER=inn earlyprintk=ttyS0,115200 systemd.log_level=err debug apic=debug
sysrq_always_enabled rcupdate.rcu_cpu_stall_timeout=100 panic=-1 softlockup_panic=1
nmi_watchdog=panic oops=panic load_ramdisk=2 prompt_ramdisk=0 console=ttyS0,115200
console=tty0 vga=normal rw ip=::::vm-intel12-yocto-x86_64-9::dhcp drbd.minor_count=8'
-initrd /fs/KVM/initrd-vm-intel12-yocto-x86_64-9 -m 320 -smp 2 -device e1000,netdev=net0
-netdev user,id=net0 -boot order=nc -no-reboot -watchdog i6300esb -rtc base=localtime
-drive file=/fs/KVM/disk0-vm-intel12-yocto-x86_64-9,media=disk,if=virtio -drive
file=/fs/KVM/disk1-vm-intel12-yocto-x86_64-9,media=disk,if=virtio -pidfile
/dev/shm/kboot/pid-vm-intel12-yocto-x86_64-9 -serial
file:/dev/shm/kboot/serial-vm-intel12-yocto-x86_64-9 -daemonize -display none -monitor
null
Thanks,
Xiaolong Ye