automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: maxime.coquelin@redhat.com
Subject: [dpdk-test-report] |FAILURE| pw21425 [PATCH v2 4/7] vhost: Add API to get MTU value
Date: 07 Mar 2017 23:43:42 -0800	[thread overview]
Message-ID: <ffb989$1mqrdu@orsmga002.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 19314 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE

http://dpdk.org/patch/21425

_Compilation issues_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Mon,  6 Mar 2017 09:27:37 +0100
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:b0c958e14dee3570a684fafb0ef5ca9c86c6f80d

Patch21425-21425 --> compile error
Build Summary: 18 Builds Done, 2 Successful, 16 Failures

Test environment and configuration as below:
OS: RHEL7.2_64
    Kernel Version:3.10.0-514.10.2.el7.x86_64
    CPU info:Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
    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-gcc
    x86_64-native-linuxapp-gcc-shared
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-64-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: RHEL7.2_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: ‘VIRTIO_NET_F_MTU’ undeclared (first use in this function)
  if (!(dev->features & VIRTIO_NET_F_MTU))
                        ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^


Failed Build #2:
OS: RHEL7.2_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: ‘VIRTIO_NET_F_MTU’ undeclared (first use in this function)
  if (!(dev->features & VIRTIO_NET_F_MTU))
                        ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^


Failed Build #3:
OS: RHEL7.2_64
Target: x86_64-native-linuxapp-gcc-shared

/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: ‘VIRTIO_NET_F_MTU’ undeclared (first use in this function)
  if (!(dev->features & VIRTIO_NET_F_MTU))
                        ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^


Failed Build #4:
OS: FC24_64
Target: x86_64-native-linuxapp-gcc-debug

/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'vhost.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_vhost' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:81: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:129: 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:104: recipe for target 'install' failed


Failed Build #5:
OS: FC24_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'vhost.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_vhost' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:81: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:129: 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:104: recipe for target 'install' failed


Failed Build #6:
OS: FC24_64
Target: x86_64-native-linuxapp-clang
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: use of undeclared identifier 'VIRTIO_DEV_READY'
        if (!(dev->flags & VIRTIO_DEV_READY))
                           ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:14: error: no member named 'mtu' in 'struct virtio_net'
        *mtu = dev->mtu;
               ~~~  ^
2 errors generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'vhost.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_vhost' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:81: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:129: 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:104: recipe for target 'install' failed


Failed Build #7:
OS: FC24_64
Target: x86_64-native-linuxapp-gcc-shared

/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'vhost.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_vhost' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:81: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:129: 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:104: recipe for target 'install' failed


Failed Build #8:
OS: FC24_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^~~~~~~~~~~~~~~~
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^~
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'vhost.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_vhost' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:81: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:129: 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:104: recipe for target 'install' failed


Failed Build #9:
OS: UB1604_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: ‘VIRTIO_NET_F_MTU’ undeclared (first use in this function)
  if (!(dev->features & VIRTIO_NET_F_MTU))
                        ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'vhost.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_vhost' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:81: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:129: 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:104: recipe for target 'install' failed


Failed Build #10:
OS: UB1604_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: ‘VIRTIO_NET_F_MTU’ undeclared (first use in this function)
  if (!(dev->features & VIRTIO_NET_F_MTU))
                        ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'vhost.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_vhost' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:81: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:129: 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:104: recipe for target 'install' failed


Failed Build #11:
OS: UB1604_64
Target: x86_64-native-linuxapp-gcc-shared

/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: ‘VIRTIO_NET_F_MTU’ undeclared (first use in this function)
  if (!(dev->features & VIRTIO_NET_F_MTU))
                        ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'vhost.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_vhost' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:81: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:129: 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:104: recipe for target 'install' failed


Failed Build #12:
OS: UB1604_64
Target: x86_64-native-linuxapp-clang
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: use of undeclared identifier 'VIRTIO_DEV_READY'
        if (!(dev->flags & VIRTIO_DEV_READY))
                           ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: use of undeclared identifier 'VIRTIO_NET_F_MTU'
        if (!(dev->features & VIRTIO_NET_F_MTU))
                              ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:14: error: no member named 'mtu' in 'struct virtio_net'
        *mtu = dev->mtu;
               ~~~  ^
3 errors generated.
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:138: recipe for target 'vhost.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:61: recipe for target 'librte_vhost' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:81: recipe for target 'lib' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:129: 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:104: recipe for target 'install' failed


Failed Build #13:
OS: CentOS7_64
Target: i686-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: ‘VIRTIO_NET_F_MTU’ undeclared (first use in this function)
  if (!(dev->features & VIRTIO_NET_F_MTU))
                        ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^


Failed Build #14:
OS: CentOS7_64
Target: x86_64-native-linuxapp-clang
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: use of undeclared identifier 'VIRTIO_DEV_READY'
        if (!(dev->flags & VIRTIO_DEV_READY))
                           ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: use of undeclared identifier 'VIRTIO_NET_F_MTU'
        if (!(dev->features & VIRTIO_NET_F_MTU))
                              ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:14: error: no member named 'mtu' in 'struct virtio_net'
        *mtu = dev->mtu;
               ~~~  ^
3 errors generated.


Failed Build #15:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc-shared

/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: ‘VIRTIO_NET_F_MTU’ undeclared (first use in this function)
  if (!(dev->features & VIRTIO_NET_F_MTU))
                        ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^


Failed Build #16:
OS: CentOS7_64
Target: x86_64-native-linuxapp-gcc
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c: In function ‘rte_vhost_mtu_get’:
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: error: ‘VIRTIO_DEV_READY’ undeclared (first use in this function)
  if (!(dev->flags & VIRTIO_DEV_READY))
                     ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:322:21: note: each undeclared identifier is reported only once for each function it appears in
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:325:24: error: ‘VIRTIO_NET_F_MTU’ undeclared (first use in this function)
  if (!(dev->features & VIRTIO_NET_F_MTU))
                        ^
/home/patchWorkOrg/compilation/lib/librte_vhost/vhost.c:328:12: error: ‘struct virtio_net’ has no member named ‘mtu’
  *mtu = dev->mtu;
            ^


DPDK STV team

             reply	other threads:[~2017-03-08  7:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  7:43 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-07 13:23 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='ffb989$1mqrdu@orsmga002.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=maxime.coquelin@redhat.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).