From: "Lu, PeipeiX" <peipeix.lu@intel.com>
To: sys_stv <sys_stv@intel.com>,
"test-report@dpdk.org" <test-report@dpdk.org>
Cc: "Xu, HuilongX" <huilongx.xu@intel.com>,
NPG-PRC-SW STV <npg-prc-sw.stv@intel.com>,
NPG-PRC-SW STV CW <npg-prc-sw.stv.cw@intel.com>
Subject: Re: [dpdk-test-report] [SUCCESS]Intel Daily DPDK Regression Test Report
Date: Tue, 10 Oct 2017 01:21:11 +0000 [thread overview]
Message-ID: <A95ECF8D0A9726439A39A44EF4CA97F20232198D@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <8a7c36$135loip@orsmga001.jf.intel.com>
Dear all,
Yesterday dpdk source code can not download, so the daily regression have a result. Now it had rerun.
-----Original Message-----
From: test-report [mailto:test-report-bounces@dpdk.org] On Behalf Of sys_stv@intel.com
Sent: Tuesday, October 10, 2017 8:10 AM
To: test-report@dpdk.org
Cc: weichunx.chen@intel.com; Xu, HuilongX <huilongx.xu@intel.com>; NPG-PRC-SW STV <npg-prc-sw.stv@intel.com>; NPG-PRC-SW STV CW <npg-prc-sw.stv.cw@intel.com>
Subject: [dpdk-test-report] [SUCCESS]Intel Daily DPDK Regression Test Report
Summary:
DPDK commit: f26ab687a74fc86455e0c98371553a53bf68c76e
Author: Jianfeng Tan <jianfeng.tan@intel.com>
Date: Thu Sep 14 024029 2017 +0000
Comment: eal: remove Xen dom0 support
next prev parent reply other threads:[~2017-10-10 1:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 0:09 sys_stv
2017-10-10 1:21 ` Lu, PeipeiX [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-12 2:50 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-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=A95ECF8D0A9726439A39A44EF4CA97F20232198D@shsmsx102.ccr.corp.intel.com \
--to=peipeix.lu@intel.com \
--cc=huilongx.xu@intel.com \
--cc=npg-prc-sw.stv.cw@intel.com \
--cc=npg-prc-sw.stv@intel.com \
--cc=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).