From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: konstantin.ananyev@intel.com
Subject: [dpdk-test-report] |FAILURE| pw35762 [PATCH RFC 2/5] bpf: add JIT compilation for x86_64 ISA.
Date: 11 Mar 2018 23:21:58 -0700 [thread overview]
Message-ID: <f7a79a$177noj@orsmga002.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 19548 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/35762
_Compilation issues_
Submitter: Konstantin Ananyev <konstantin.ananyev@intel.com>
Date: Thu, 8 Mar 2018 01:29:58 +0000
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:c06ddf9698e0c2a9653cfa971f9ddc205065662c
Patch35761-35762 --> compile error
Build Summary: 15 Builds Done, 2 Successful, 13 Failures
Test environment and configuration as below:
OS: FreeBSD10.3_64
Kernel Version:10.3-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.97-MHz K8-class CPU)
GCC Version:gcc (FreeBSD Ports Collection) 4.8.5
Clang Version:3.4.1
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc
OS: FC24_64
Kernel Version:4.9.13-100.fc24.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
Clang Version:3.8.0
x86_64-native-linuxapp-gcc-debug
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
OS: UB1604_64
Kernel Version:4.4.0-78-generic
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Clang Version:3.8.0
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-clang
OS: CentOS7_64
Kernel Version:3.10.0-514.10.2.el7.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
Clang Version:3.4.2
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
Failed Build #1:
OS: FC24_64
Target: x86_64-native-linuxapp-gcc-debug
SYMLINK-FILE include/rte_bpf.h/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c: In function ‘bpf_exec’:
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: error: ‘BPF_JLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLT | BPF_K):
^~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:351:19: error: ‘BPF_JLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLE | BPF_K):
^~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:357:19: error: ‘BPF_JSLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLT | BPF_K):
^~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:363:19: error: ‘BPF_JSLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLE | BPF_K):
^~~~~~~~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'bpf_exec.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_bpf' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #2:
OS: FC24_64
Target: i686-native-linuxapp-gcc
SYMLINK-FILE include/rte_bpf.h/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c: In function ‘bpf_exec’:
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: error: ‘BPF_JLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLT | BPF_K):
^~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:351:19: error: ‘BPF_JLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLE | BPF_K):
^~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:357:19: error: ‘BPF_JSLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLT | BPF_K):
^~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:363:19: error: ‘BPF_JSLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLE | BPF_K):
^~~~~~~~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'bpf_exec.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_bpf' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #3:
OS: FC24_64
Target: x86_64-native-linuxapp-clang
SYMLINK-FILE include/rte_bpf.h/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: error: use of undeclared identifier 'BPF_JLT'
case (BPF_JMP | BPF_JLT | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:351:19: error: use of undeclared identifier 'BPF_JLE'
case (BPF_JMP | BPF_JLE | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:357:19: error: use of undeclared identifier 'BPF_JSLT'
case (BPF_JMP | BPF_JSLT | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:363:19: error: use of undeclared identifier 'BPF_JSLE'
case (BPF_JMP | BPF_JSLE | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:379:19: error: use of undeclared identifier 'BPF_JLT'
case (BPF_JMP | BPF_JLT | BPF_X):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:385:19: error: use of undeclared identifier 'BPF_JLE'
case (BPF_JMP | BPF_JLE | BPF_X):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:391:19: error: use of undeclared identifier 'BPF_JSLT'
case (BPF_JMP | BPF_JSLT | BPF_X):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:397:19: error: use of undeclared identifier 'BPF_JSLE'
case (BPF_JMP | BPF_JSLE | BPF_X):
^
8 errors generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'bpf_exec.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_bpf' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #4:
OS: FC24_64
Target: x86_64-native-linuxapp-gcc-shared
SYMLINK-FILE include/rte_bpf.h/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c: In function ‘bpf_exec’:
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: error: ‘BPF_JLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLT | BPF_K):
^~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:351:19: error: ‘BPF_JLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLE | BPF_K):
^~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:357:19: error: ‘BPF_JSLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLT | BPF_K):
^~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:363:19: error: ‘BPF_JSLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLE | BPF_K):
^~~~~~~~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'bpf_exec.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_bpf' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #5:
OS: FC24_64
Target: x86_64-native-linuxapp-gcc
SYMLINK-FILE include/rte_bpf.h/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c: In function ‘bpf_exec’:
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: error: ‘BPF_JLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLT | BPF_K):
^~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:351:19: error: ‘BPF_JLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLE | BPF_K):
^~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:357:19: error: ‘BPF_JSLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLT | BPF_K):
^~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:363:19: error: ‘BPF_JSLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLE | BPF_K):
^~~~~~~~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'bpf_exec.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_bpf' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #6:
OS: UB1604_64
Target: i686-native-linuxapp-gcc
SYMLINK-FILE include/rte_bpf.h/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c: In function ‘bpf_exec’:
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: error: ‘BPF_JLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLT | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:351:19: error: ‘BPF_JLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLE | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:357:19: error: ‘BPF_JSLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLT | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:363:19: error: ‘BPF_JSLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLE | BPF_K):
^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'bpf_exec.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_bpf' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #7:
OS: UB1604_64
Target: x86_64-native-linuxapp-gcc
SYMLINK-FILE include/rte_bpf.h/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c: In function ‘bpf_exec’:
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: error: ‘BPF_JLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLT | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:351:19: error: ‘BPF_JLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLE | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:357:19: error: ‘BPF_JSLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLT | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:363:19: error: ‘BPF_JSLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLE | BPF_K):
^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'bpf_exec.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_bpf' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #8:
OS: UB1604_64
Target: x86_64-native-linuxapp-gcc-shared
SYMLINK-FILE include/rte_bpf.h/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c: In function ‘bpf_exec’:
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: error: ‘BPF_JLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLT | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:351:19: error: ‘BPF_JLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JLE | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:357:19: error: ‘BPF_JSLT’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLT | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:363:19: error: ‘BPF_JSLE’ undeclared (first use in this function)
case (BPF_JMP | BPF_JSLE | BPF_K):
^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'bpf_exec.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_bpf' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #9:
OS: UB1604_64
Target: x86_64-native-linuxapp-clang
SYMLINK-FILE include/rte_bpf.h/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:345:19: error: use of undeclared identifier 'BPF_JLT'
case (BPF_JMP | BPF_JLT | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:351:19: error: use of undeclared identifier 'BPF_JLE'
case (BPF_JMP | BPF_JLE | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:357:19: error: use of undeclared identifier 'BPF_JSLT'
case (BPF_JMP | BPF_JSLT | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:363:19: error: use of undeclared identifier 'BPF_JSLE'
case (BPF_JMP | BPF_JSLE | BPF_K):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:379:19: error: use of undeclared identifier 'BPF_JLT'
case (BPF_JMP | BPF_JLT | BPF_X):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:385:19: error: use of undeclared identifier 'BPF_JLE'
case (BPF_JMP | BPF_JLE | BPF_X):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:391:19: error: use of undeclared identifier 'BPF_JSLT'
case (BPF_JMP | BPF_JSLT | BPF_X):
^
/home/patchWorkOrg/compilation/lib/librte_bpf/bpf_exec.c:397:19: error: use of undeclared identifier 'BPF_JSLE'
case (BPF_JMP | BPF_JSLE | BPF_X):
^
8 errors generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:114: recipe for target 'bpf_exec.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'librte_bpf' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #10:
OS: CentOS7_64
Target: i686-native-linuxapp-gcc
SYMLINK-FILE include/rte_bpf.hIn file included from /home/patchWorkOrg/compilation/lib/librte_bpf/bpf_impl.h:8:0,
from /home/patchWorkOrg/compilation/lib/librte_bpf/bpf.c:15:
/home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_bpf.h:10:23: fatal error: linux/bpf.h: No such file or directory
#include <linux/bpf.h>
^
compilation terminated.
Failed Build #11:
OS: CentOS7_64
Target: x86_64-native-linuxapp-clang
SYMLINK-FILE include/rte_bpf.hIn file included from /home/patchWorkOrg/compilation/lib/librte_bpf/bpf.c:15:
In file included from /home/patchWorkOrg/compilation/lib/librte_bpf/bpf_impl.h:8:
/home/patchWorkOrg/compilation/x86_64-native-linuxapp-clang/include/rte_bpf.h:10:10: fatal error: 'linux/bpf.h' file not found
#include <linux/bpf.h>
^
1 error generated.
Failed Build #12:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc-shared
SYMLINK-FILE include/rte_bpf.hIn file included from /home/patchWorkOrg/compilation/lib/librte_bpf/bpf_impl.h:8:0,
from /home/patchWorkOrg/compilation/lib/librte_bpf/bpf.c:15:
/home/patchWorkOrg/compilation/x86_64-native-linuxapp-gcc/include/rte_bpf.h:10:23: fatal error: linux/bpf.h: No such file or directory
#include <linux/bpf.h>
^
compilation terminated.
Failed Build #13:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc
SYMLINK-FILE include/rte_bpf.hIn file included from /home/patchWorkOrg/compilation/lib/librte_bpf/bpf_impl.h:8:0,
from /home/patchWorkOrg/compilation/lib/librte_bpf/bpf.c:15:
/home/patchWorkOrg/compilation/x86_64-native-linuxapp-gcc/include/rte_bpf.h:10:23: fatal error: linux/bpf.h: No such file or directory
#include <linux/bpf.h>
^
compilation terminated.
DPDK STV team
reply other threads:[~2018-03-12 6:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='f7a79a$177noj@orsmga002.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=test-report@dpdk.org \
/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).