From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |SUCCESS| pw48359[v1] net/i40e: fix VF port reset
Date: 28 Nov 2018 01:52:51 -0800 [thread overview]
Message-ID: <0590c7$3bl4fa@orsmga001.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]
Test-Label: Intel-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/48359
_Compilation OK_
Submitter: Zhirun Yan <zhirun.yan@intel.com>
Date: 2018-11-28 16:52:12
DPDK git baseline: Repo:dpdk-master, CommitID: 0da7f445df445630c794897347ee360d6fe6348b
Build Summary: 15 Builds Done, 15 Successful, 0 Failures
Test environment and configuration as below:
OS: FC25
Kernel Version: 4.5.5-300.fc24.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (GCC) 6.1.1 20160510 (Red Hat 6.1.1-2)
Clang Version: 3.8.0 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-debug
OS: FC24
Kernel Version: 4.11.12-100.fc24.x86_64
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (GCC) 6.3.1 20161221 (Red Hat 6.3.1-1)
Clang Version: 3.8.1 (tags/RELEASE_381/final)
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc-shared
OS: CENTOS
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 (tags/RELEASE_34/dot2-final)
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
OS: UB1604
Kernel Version: 4.4.0-137-generic
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version: gcc (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
Clang Version: 3.8.0-2ubuntu4 (tags/RELEASE_380/final)
x86_64-native-linuxapp-gcc
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc-shared
OS: FreeBSD
Kernel Version: 10.3-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz (2294.75-MHz K8-class CPU)
GCC Version: gcc (FreeBSD Ports Collection) 7.3.0
Clang Version: 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc
DPDK STV team
next reply other threads:[~2018-11-28 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 9:52 sys_stv [this message]
[not found] <20181128165212.78742-1-zhirun.yan@intel.com>
2018-11-28 9:16 ` [dpdk-test-report] |SUCCESS| pw48359 [v1] " checkpatch
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='0590c7$3bl4fa@orsmga001.jf.intel.com' \
--to=sys_stv@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).