From: sys_stv@intel.com
To: weichunx.chen@intel.com, haifengx.tang@intel.com,
yufengx.mo@intel.com, yong.liu@intel.com,
thomas.monjalon@6wind.com, dts@dpdk.org, qian.q.xu@intel.com,
waterman.cao@intel.com, shide.dong@intel.com
Subject: [dts] |SUCCESS| pw 6975-6978 [dpdk-dev, v2, 4/4] ethdev: check driver support for functions
Date: 09 Sep 2015 18:02:37 -0700 [thread overview]
Message-ID: <c45ac1$j44lc6@orsmga003.jf.intel.com> (raw)
Summary:
=====================================================================================================================================================================================
| DPDK git baseline | 17e01e3141aa520042eb1fa705b3472757350bab
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Patchwork ID | 6975-6978 | http://www.dpdk.org/dev/patchwork/patch/6978/
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Submitter | "Richardson, Bruce" <bruce.richardson@intel.com>
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Date | Wed, 9 Sep 2015 16:09:34 +0100
=====================================================================================================================================================================================
| OS | Nic |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| fedora | niantic |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| i686-native-linuxapp-gcc | compile pass
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| x86_64-native-linuxapp-gcc | compile pass
=====================================================================================================================================================================================
| DTS validation
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| OS | Nic | TestType | Kernel | GCC | Target | Result(F/T)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| fedora | Niantic | auto | | 4 | x86_64-native-linuxapp-gcc| total 5, pass 5, failed 0
=====================================================================================================================================================================================
Failed Case List:
========================================================================================================================================
\ | | | |
\Target| | | |
\ | x86_64-native-linuxapp-gcc | i686-native-linuxapp-gcc | x86_64-native-bsdapp-gcc |
OS \ | | | |
\| | | |
----------------------------------------------------------------------------------------------------------------------------------------
fedora | N/A | N/A | N/A |
========================================================================================================================================
DPDK STV team
reply other threads:[~2015-09-10 1:02 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='c45ac1$j44lc6@orsmga003.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=dts@dpdk.org \
--cc=haifengx.tang@intel.com \
--cc=qian.q.xu@intel.com \
--cc=shide.dong@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=waterman.cao@intel.com \
--cc=weichunx.chen@intel.com \
--cc=yong.liu@intel.com \
--cc=yufengx.mo@intel.com \
/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).