From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: juanx.xia@intel.com, huilongx.xu@intel.com,
npg-prc-sw.stv@intel.com, npg-prc-sw.stv.cw@intel.com
Subject: [dpdk-test-report] [SUCCESS]Intel Daily DPDK Regression Test Report
Date: 11 Sep 2018 19:50:46 -0700 [thread overview]
Message-ID: <ca5293$2l2qkf@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
Summary:
Test Result Path:
\\10.240.176.131\dpdk_test_result\2018-09-11_20-30-47_3605968c2fa783674624562a7dfab256eb9044ea
DPDK commit: 3605968c2fa783674624562a7dfab256eb9044ea
Author: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Mon Aug 27 142223 2018 +0530
Comment: bus/fslmc: fix undefined reference of memsegs
UB1710
Kernel: 4.13.0-16-generic
GCC: 7.2.0
NIC: VFIO_Niantic_uio_pci
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/13
next reply other threads:[~2018-09-12 2:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 2:50 sys_stv [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-28 0:11 sys_stv
2018-12-20 0:05 sys_stv
2018-12-14 0:11 sys_stv
2018-12-13 0:03 sys_stv
2018-12-06 0:00 sys_stv
2018-12-05 0:05 sys_stv
2018-12-04 1:26 sys_stv
2018-11-29 0:01 sys_stv
2018-10-31 0:10 sys_stv
2018-10-12 0:10 sys_stv
2018-09-17 0:28 sys_stv
2018-09-16 0:26 sys_stv
2018-09-03 2:48 sys_stv
2018-08-20 0:25 sys_stv
2018-08-19 0:19 sys_stv
2018-07-31 0:13 sys_stv
2017-10-10 0:09 sys_stv
2017-10-10 1:21 ` Lu, PeipeiX
2017-10-09 8:24 sys_stv
2017-07-09 0:04 sys_stv
2017-07-07 0:04 sys_stv
2017-07-03 0:10 sys_stv
2017-07-02 0:04 sys_stv
2017-06-30 0:14 sys_stv
2017-06-29 0:14 sys_stv
2017-06-21 1:07 sys_stv
2017-04-01 0:07 sys_stv
2016-12-09 0:06 sys_stv
2016-12-08 0:02 sys_stv
2016-12-02 1:27 sys_stv
2016-11-28 0:04 sys_stv
2016-11-27 0:02 sys_stv
2016-11-25 0:01 sys_stv
2016-11-24 0:01 sys_stv
2016-11-22 0:10 sys_stv
2016-11-20 0:10 sys_stv
2016-11-19 0:01 sys_stv
2016-11-18 0:04 sys_stv
2016-11-17 0:01 sys_stv
2016-11-16 0: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='ca5293$2l2qkf@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=huilongx.xu@intel.com \
--cc=juanx.xia@intel.com \
--cc=npg-prc-sw.stv.cw@intel.com \
--cc=npg-prc-sw.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).