From: sys_stv@intel.com
To: test-report@dpdk.org, thomas@monjalon.net
Cc: dpdk_sw_eng@intel.com, npg.sw.core.tools.prc@intel.com
Subject: [dpdk-test-report] |FAILURE| dpdk-next-net-mrvl daily Intel builds
Date: 17 May 2022 03:55:16 -0700 [thread overview]
Message-ID: <8ea9f5$l8nfgk@fmsmga001-auth.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 18282 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
_Compilation issues_
commit 1d129cd2b63cae425ae807e9e0a11084c2d4fad9
Author: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Sun May 8 13:18:39 2022 +0530
common/cnxk: add support for per-port RQ in inline device
DPDK git Repo: dpdk-next-net-mrvl
Meson Build Summary: 24 Builds Done, 23 Successful, 1 Failures, 0 Blocked
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| os | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
| FC36-64 | fail | pass | | | | | |
| FreeBSD13-64 | pass | pass | | pass | pass | | |
| RHEL86-64 | pass | pass | | pass | pass | | |
| SUSE15-64 | pass | pass | | | | | |
| UB2004-32 | pass | | | | | | |
| UB2004-64 | pass | pass | | | | pass | |
| UB2204-32 | pass | | | | | | |
| UB2204-64N | pass | | | pass | | | |
| UB2204-64 | pass | pass | | | | pass | pass |
| CentOS79-64 | pass | | | | | | |
+--------------+------------+--------------+------------+------------+-----------+----------+------------+
Comments:
Because of DPDK bug (https://bugs.dpdk.org/show_bug.cgi?id=928),
All the dpdk-next-* branch add `Ddisable_drivers=event/cnxk` option when build with ICC complier.
Test environment and configuration as below:
OS: FC36-64
Kernel Version: 5.17.7-300.fc36.x86_64
GCC Version: gcc (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1)
Clang Version: 14.0.0 (Fedora 14.0.0-1.fc36)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: FreeBSD13-64
Kernel Version: 13.0-RELEASE
GCC Version: gcc (FreeBSD Ports Collection) 10.3.0
Clang Version: 11.0.1 (git@github.com:llvm/llvm-project.git llvmorg-11.0.1-0-g43ff75f2c3fe)
x86_64-native-bsdapp-gcc
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc+shared
x86_64-native-bsdapp-gcc+debug
OS: RHEL86-64
Kernel Version: 4.18.0-372.9.1.el8.x86_64
GCC Version: gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-13)
Clang Version: 14.0.0 (Red Hat 14.0.0-1.module_el8.7.0+1142+5343df54)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc+shared
x86_64-native-linuxapp-gcc+debug
OS: SUSE15-64
Kernel Version: 5.3.18-57-default
GCC Version: gcc (SUSE Linux) 7.5.0
Clang Version: 11.0.1
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
OS: UB2004-32
Kernel Version: 5.8.0-48-generic
GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
Clang Version: 10.0.0-4ubuntu1
i686-native-linuxapp-gcc
OS: UB2004-64
Kernel Version: 5.8.0-48-generic
GCC Version: gcc (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
Clang Version: 10.0.0-4ubuntu1
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-doc
OS: UB2204-32
Kernel Version: 5.15.0-25-generic
GCC Version: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
Clang Version: NA
i686-native-linuxapp-gcc
OS: UB2204-64N
Kernel Version: 5.17.5-051705-generic
GCC Version: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
Clang Version: 14.0.0-1ubuntu1
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc+shared
OS: UB2204-64
Kernel Version: 5.15.0-25-generic
GCC Version: gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
Clang Version: 14.0.0-1ubuntu1
x86_64-native-linuxapp-gcc+16byte
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-doc
OS: CentOS79-64
Kernel Version: 3.10.0-1160.el7.x86_64
GCC Version: gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44)
Clang Version: 3.4.2 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-gcc
*Build Failed #1:
OS: FC36-64
Target: x86_64-native-linuxapp-gcc
FAILED: lib/librte_vhost.a.p/vhost_vhost_crypto.c.o
gcc -Ilib/librte_vhost.a.p -Ilib -I../lib -Ilib/vhost -I../lib/vhost -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/ethdev -I../lib/ethdev -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/meter -I../lib/meter -Ilib/cryptodev -I../lib/cryptodev -Ilib/rcu -I../lib/rcu -Ilib/hash -I../lib/hash -Ilib/pci -I../lib/pci -Ilib/dmadev -I../lib/dmadev -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -O3 -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-address-of-packed-member -Wno-packed-not-aligned -Wno-missing-field-initializers -Wno-zero-length-bounds -D_GNU_SOURCE -fPIC -march=native -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DVHOST_GCC_UNROLL_PRAGMA -fno-strict-aliasing -DRTE_LOG_DEFAULT_LOGTYPE=lib.vhost -MD -MQ lib/librte_vhost.a.p/vhost_vhost_crypto.c.o -MF lib/librte_vhost.a.p/vhost_vhost_crypto.c.o.d -o lib/librte_vhost.a.p/vhost_vhost_crypto.c.o -c ../lib/vhost/vhost_crypto.c
In file included from /usr/lib/gcc/x86_64-redhat-linux/12/include/immintrin.h:43,
from /usr/lib/gcc/x86_64-redhat-linux/12/include/x86intrin.h:32,
from ../lib/eal/x86/include/rte_vect.h:31,
from ../lib/eal/x86/include/rte_memcpy.h:17,
from ../lib/mempool/rte_mempool.h:46,
from ../lib/mbuf/rte_mbuf.h:38,
from ../lib/vhost/vhost_crypto.c:7:
In function ‘_mm256_storeu_si256’,
inlined from ‘rte_mov32’ at ../lib/eal/x86/include/rte_memcpy.h:320:2,
inlined from ‘rte_mov128’ at ../lib/eal/x86/include/rte_memcpy.h:343:2,
inlined from ‘rte_memcpy_generic’ at ../lib/eal/x86/include/rte_memcpy.h:438:4,
inlined from ‘rte_memcpy’ at ../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from ‘copy_data’ at ../lib/vhost/vhost_crypto.c:588:2,
inlined from ‘vhost_crypto_process_one_req’ at ../lib/vhost/vhost_crypto.c:1256:6,
inlined from ‘rte_vhost_crypto_fetch_requests’ at ../lib/vhost/vhost_crypto.c:1656:8:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:935:8: error: array subscript ‘__m256i_u[2]’ is partly outside array bounds of ‘struct virtio_crypto_op_data_req[1]’ [-Werror=array-bounds]
935 | *__P = __A;
| ~~~~~^~~~~
../lib/vhost/vhost_crypto.c: In function ‘rte_vhost_crypto_fetch_requests’:
../lib/vhost/vhost_crypto.c:1178:42: note: at offset 64 into object ‘req’ of size 72
1178 | struct virtio_crypto_op_data_req req;
| ^~~
In function ‘_mm256_storeu_si256’,
inlined from ‘rte_mov32’ at ../lib/eal/x86/include/rte_memcpy.h:320:2,
inlined from ‘rte_mov128’ at ../lib/eal/x86/include/rte_memcpy.h:344:2,
inlined from ‘rte_memcpy_generic’ at ../lib/eal/x86/include/rte_memcpy.h:438:4,
inlined from ‘rte_memcpy’ at ../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from ‘copy_data’ at ../lib/vhost/vhost_crypto.c:588:2,
inlined from ‘vhost_crypto_process_one_req’ at ../lib/vhost/vhost_crypto.c:1256:6,
inlined from ‘rte_vhost_crypto_fetch_requests’ at ../lib/vhost/vhost_crypto.c:1656:8:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:935:8: error: array subscript 3 is outside array bounds of ‘struct virtio_crypto_op_data_req[1]’ [-Werror=array-bounds]
935 | *__P = __A;
| ~~~~~^~~~~
../lib/vhost/vhost_crypto.c: In function ‘rte_vhost_crypto_fetch_requests’:
../lib/vhost/vhost_crypto.c:1178:42: note: at offset 96 into object ‘req’ of size 72
1178 | struct virtio_crypto_op_data_req req;
| ^~~
In function ‘_mm256_storeu_si256’,
inlined from ‘rte_mov32’ at ../lib/eal/x86/include/rte_memcpy.h:320:2,
inlined from ‘rte_memcpy_generic’ at ../lib/eal/x86/include/rte_memcpy.h:450:4,
inlined from ‘rte_memcpy’ at ../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from ‘copy_data’ at ../lib/vhost/vhost_crypto.c:588:2,
inlined from ‘vhost_crypto_process_one_req’ at ../lib/vhost/vhost_crypto.c:1256:6,
inlined from ‘rte_vhost_crypto_fetch_requests’ at ../lib/vhost/vhost_crypto.c:1656:8:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:935:8: error: array subscript ‘__m256i_u[2]’ is partly outside array bounds of ‘void[72]’ [-Werror=array-bounds]
935 | *__P = __A;
| ~~~~~^~~~~
../lib/vhost/vhost_crypto.c: In function ‘rte_vhost_crypto_fetch_requests’:
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [0, 64] into object ‘req’ of size 72
1178 | struct virtio_crypto_op_data_req req;
| ^~~
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 72] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [128, 192] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [0, 64] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 72] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [128, 192] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [0, 64] into object ‘req’ of size 72
In function ‘_mm256_storeu_si256’,
inlined from ‘rte_mov32’ at ../lib/eal/x86/include/rte_memcpy.h:320:2,
inlined from ‘rte_memcpy_generic’ at ../lib/eal/x86/include/rte_memcpy.h:451:4,
inlined from ‘rte_memcpy’ at ../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from ‘copy_data’ at ../lib/vhost/vhost_crypto.c:588:2,
inlined from ‘vhost_crypto_process_one_req’ at ../lib/vhost/vhost_crypto.c:1256:6,
inlined from ‘rte_vhost_crypto_fetch_requests’ at ../lib/vhost/vhost_crypto.c:1656:8:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:935:8: error: array subscript ‘__m256i_u[2]’ is partly outside array bounds of ‘void[72]’ [-Werror=array-bounds]
935 | *__P = __A;
| ~~~~~^~~~~
../lib/vhost/vhost_crypto.c: In function ‘rte_vhost_crypto_fetch_requests’:
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 65] into object ‘req’ of size 72
1178 | struct virtio_crypto_op_data_req req;
| ^~~
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [2, 72] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [129, 193] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 65] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [2, 72] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [129, 193] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 65] into object ‘req’ of size 72
In function ‘_mm256_storeu_si256’,
inlined from ‘rte_mov32’ at ../lib/eal/x86/include/rte_memcpy.h:320:2,
inlined from ‘rte_mov128’ at ../lib/eal/x86/include/rte_memcpy.h:343:2,
inlined from ‘rte_memcpy_generic’ at ../lib/eal/x86/include/rte_memcpy.h:438:4,
inlined from ‘rte_memcpy’ at ../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from ‘copy_data’ at ../lib/vhost/vhost_crypto.c:588:2,
inlined from ‘vhost_crypto_process_one_req’ at ../lib/vhost/vhost_crypto.c:1256:6,
inlined from ‘rte_vhost_crypto_fetch_requests’ at ../lib/vhost/vhost_crypto.c:1685:8:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:935:8: error: array subscript ‘__m256i_u[2]’ is partly outside array bounds of ‘struct virtio_crypto_op_data_req[1]’ [-Werror=array-bounds]
935 | *__P = __A;
| ~~~~~^~~~~
../lib/vhost/vhost_crypto.c: In function ‘rte_vhost_crypto_fetch_requests’:
../lib/vhost/vhost_crypto.c:1178:42: note: at offset 64 into object ‘req’ of size 72
1178 | struct virtio_crypto_op_data_req req;
| ^~~
In function ‘_mm256_storeu_si256’,
inlined from ‘rte_mov32’ at ../lib/eal/x86/include/rte_memcpy.h:320:2,
inlined from ‘rte_mov128’ at ../lib/eal/x86/include/rte_memcpy.h:344:2,
inlined from ‘rte_memcpy_generic’ at ../lib/eal/x86/include/rte_memcpy.h:438:4,
inlined from ‘rte_memcpy’ at ../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from ‘copy_data’ at ../lib/vhost/vhost_crypto.c:588:2,
inlined from ‘vhost_crypto_process_one_req’ at ../lib/vhost/vhost_crypto.c:1256:6,
inlined from ‘rte_vhost_crypto_fetch_requests’ at ../lib/vhost/vhost_crypto.c:1685:8:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:935:8: error: array subscript 3 is outside array bounds of ‘struct virtio_crypto_op_data_req[1]’ [-Werror=array-bounds]
935 | *__P = __A;
| ~~~~~^~~~~
../lib/vhost/vhost_crypto.c: In function ‘rte_vhost_crypto_fetch_requests’:
../lib/vhost/vhost_crypto.c:1178:42: note: at offset 96 into object ‘req’ of size 72
1178 | struct virtio_crypto_op_data_req req;
| ^~~
In function ‘_mm256_storeu_si256’,
inlined from ‘rte_mov32’ at ../lib/eal/x86/include/rte_memcpy.h:320:2,
inlined from ‘rte_memcpy_generic’ at ../lib/eal/x86/include/rte_memcpy.h:450:4,
inlined from ‘rte_memcpy’ at ../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from ‘copy_data’ at ../lib/vhost/vhost_crypto.c:588:2,
inlined from ‘vhost_crypto_process_one_req’ at ../lib/vhost/vhost_crypto.c:1256:6,
inlined from ‘rte_vhost_crypto_fetch_requests’ at ../lib/vhost/vhost_crypto.c:1685:8:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:935:8: error: array subscript ‘__m256i_u[2]’ is partly outside array bounds of ‘void[72]’ [-Werror=array-bounds]
935 | *__P = __A;
| ~~~~~^~~~~
../lib/vhost/vhost_crypto.c: In function ‘rte_vhost_crypto_fetch_requests’:
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [0, 64] into object ‘req’ of size 72
1178 | struct virtio_crypto_op_data_req req;
| ^~~
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 72] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [128, 192] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [0, 64] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 72] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [128, 192] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [0, 64] into object ‘req’ of size 72
In function ‘_mm256_storeu_si256’,
inlined from ‘rte_mov32’ at ../lib/eal/x86/include/rte_memcpy.h:320:2,
inlined from ‘rte_memcpy_generic’ at ../lib/eal/x86/include/rte_memcpy.h:451:4,
inlined from ‘rte_memcpy’ at ../lib/eal/x86/include/rte_memcpy.h:882:10,
inlined from ‘copy_data’ at ../lib/vhost/vhost_crypto.c:588:2,
inlined from ‘vhost_crypto_process_one_req’ at ../lib/vhost/vhost_crypto.c:1256:6,
inlined from ‘rte_vhost_crypto_fetch_requests’ at ../lib/vhost/vhost_crypto.c:1685:8:
/usr/lib/gcc/x86_64-redhat-linux/12/include/avxintrin.h:935:8: error: array subscript ‘__m256i_u[2]’ is partly outside array bounds of ‘void[72]’ [-Werror=array-bounds]
935 | *__P = __A;
| ~~~~~^~~~~
../lib/vhost/vhost_crypto.c: In function ‘rte_vhost_crypto_fetch_requests’:
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 65] into object ‘req’ of size 72
1178 | struct virtio_crypto_op_data_req req;
| ^~~
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [2, 72] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [129, 193] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 65] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [2, 72] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [129, 193] into object ‘req’ of size 72
../lib/vhost/vhost_crypto.c:1178:42: note: at offset [1, 65] into object ‘req’ of size 72
cc1: all warnings being treated as errors
[649/3545] Linking target drivers/librte_common_iavf.so.22.2
[650/3545] Generating rte_bus_auxiliary.sym_chk with a custom command (wrapped by meson to capture output)
[651/3545] Generating symbol file drivers/librte_common_octeontx.so.22.2.p/librte_common_octeontx.so.22.2.symbols
[652/3545] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_fman_fman.c.o
[653/3545] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_qbman_process.c.o
[654/3545] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_qbman_dpaa_alloc.c.o
[655/3545] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_qbman_bman_driver.c.o
[656/3545] Compiling C object drivers/libtmp_rte_bus_dpaa.a.p/bus_dpaa_base_qbman_dpaa_sys.c.o
[657/3545] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_table_action.c.o
ninja: build stopped
DPDK STV team
next reply other threads:[~2022-05-17 10:55 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 10:55 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-22 13:51 sys_stv
2023-05-17 16:43 sys_stv
2023-05-15 23:35 sys_stv
2023-01-09 23:17 sys_stv
2023-01-09 15:50 sys_stv
2023-01-09 8:03 sys_stv
2022-11-23 23:35 sys_stv
2022-11-23 7:53 sys_stv
2022-10-31 4:24 sys_stv
2022-10-13 22:59 sys_stv
2022-09-20 10:38 sys_stv
2022-09-16 11:39 sys_stv
2022-09-14 22:39 sys_stv
2022-06-26 22:24 sys_stv
2022-06-25 22:22 sys_stv
2022-06-24 22:22 sys_stv
2022-06-16 22:20 sys_stv
2022-06-14 6:40 sys_stv
2022-06-10 22:21 sys_stv
2022-06-09 22:20 sys_stv
2022-06-08 22:21 sys_stv
2022-06-06 22:22 sys_stv
2022-06-01 23:26 sys_stv
2022-06-01 22:21 sys_stv
2022-05-31 23:32 sys_stv
2022-05-31 22:21 sys_stv
2022-05-31 11:37 sys_stv
2022-05-31 5:36 sys_stv
2022-05-30 22:22 sys_stv
2022-05-24 22:22 sys_stv
2022-05-18 23:39 sys_stv
2022-05-18 22:24 sys_stv
2022-05-17 23:41 sys_stv
2022-05-17 22:24 sys_stv
2022-05-17 17:50 sys_stv
2022-05-16 22:35 sys_stv
2022-05-07 5:58 sys_stv
2022-05-06 22:33 sys_stv
2022-01-29 5:58 sys_stv
2022-01-29 5:44 sys_stv
2022-01-29 5:41 sys_stv
2022-01-29 5:29 sys_stv
2022-01-29 4:15 sys_stv
2022-01-29 3:59 sys_stv
2022-01-28 11:43 sys_stv
2022-01-28 10:15 sys_stv
2022-01-28 5:28 sys_stv
2022-01-27 23:37 sys_stv
2022-01-27 17:37 sys_stv
2022-01-27 11:38 sys_stv
2022-01-27 6:00 sys_stv
2022-01-27 5:04 sys_stv
2022-01-27 4:19 sys_stv
2022-01-26 23:04 sys_stv
2022-01-26 17:08 sys_stv
2022-01-26 5:04 sys_stv
2022-01-26 2:38 sys_stv
2022-01-25 22:43 sys_stv
2022-01-25 16:53 sys_stv
2022-01-25 9:08 sys_stv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='8ea9f5$l8nfgk@fmsmga001-auth.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=dpdk_sw_eng@intel.com \
--cc=npg.sw.core.tools.prc@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).