From: sys_stv@intel.com
To: jasvinder.singh@intel.com,test-report@dpdk.org
Subject: [dpdk-test-report] [Patchwork]|SUCCESS| pw16660 examples/ip_pipeline: fix freeBSD build error
Date: 17 Oct 2016 09:08:18 -0700 [thread overview]
Message-ID: <532f2c$ve5ch1@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
Test-Label: Intel Niantic on Fedora
Test-Status: SUCCESS
Patchwork ID: 16660
http://www.dpdk.org/dev/patchwork/patch/16660/
Submitter: Jasvinder Singh <jasvinder.singh@intel.com>
Date: Mon, 17 Oct 2016 16:48:57 +0100
DPDK git baseline: 17351105097ffc13e42e6b2b9b0ee6c6c2cb802d
Check patch:Success
Compilation:
OS: fedora
Nic: niantic
GCC: gcc_x86-64, 4.8.3
ICC:16.0.2
i686-native-linuxapp-icc: compile pass
x86_64-native-linuxapp-gcc-combined: compile pass
i686-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-gcc: compile pass
x86_64-native-linuxapp-icc: compile pass
x86_64-native-linuxapp-gcc-debug: compile pass
x86_64-native-linuxapp-gcc-shared: compile pass
x86_64-native-linuxapp-clang: compile pass
DPDK STV team
reply other threads:[~2016-10-17 16:08 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='532f2c$ve5ch1@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=jasvinder.singh@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).