Michal Privoznik bd11c753f3 virsysinfo: Calculate OEM string index better ... As can be seen in earlier commits, there can be two OEM strings with the same index. But since our parser (virSysinfoParseOEMStrings()) doesn't expect that, it increments index in each run and thus skips over these strings. Fortunately, we have the right index at hand - we're just skipping over it in a loop. Just reconstruct the index back inside the loop. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Jiri Denemark <jdenemar@redhat.com>		2024-07-25 16:51:17 +02:00
..
aarch64-gigabytecpuinfo.data
aarch64-gigabytesysinfo.data
aarch64-gigabytesysinfo.expect
aarch64-hpe-apollosysinfo.data	tests: Add HPE Apollo test case to sysinfotest	2024-07-25 16:49:45 +02:00
aarch64-hpe-apollosysinfo.expect	virsysinfo: Calculate OEM string index better	2024-07-25 16:51:17 +02:00
aarch64-moonshotcpuinfo.data
aarch64-moonshotsysinfo.expect
aarch64cpuinfo.data
aarch64sysinfo.expect
arm-rpi2cpuinfo.data
arm-rpi2sysinfo.expect
armcpuinfo.data
armsysinfo.expect
ppccpuinfo.data
ppcsysinfo.expect
s390-freqcpuinfo.data
s390-freqsysinfo.data
s390-freqsysinfo.expect
s390cpuinfo.data
s390sysinfo.data
s390sysinfo.expect
x86sysinfo.data
x86sysinfo.expect