From: "Zhan, Zhaochen" <zhaochen.zhan@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCHv5] librte_acl make it build/work for 'default' target
Date: Thu, 25 Sep 2014 07:52:17 +0000 [thread overview]
Message-ID: <6D0EE020084B194084D70B0A8D2207B8ED8B26@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1409585324-6829-1-git-send-email-konstantin.ananyev@intel.com>
Tested-by: Zhaochen Zhan <zhaochen.zhan@intel.com>
This patch has been verified both on "native" and "default" target.
Please see environment information as the following:
CPU: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
OS: Linux fc20 3.11.10-301.fc20.x86_64
GCC: 4.8.3
NIC: Intel Niantic 82599
prev parent reply other threads:[~2014-09-25 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 15:28 Konstantin Ananyev
2014-09-02 13:43 ` Neil Horman
2014-09-03 1:29 ` Thomas Monjalon
2014-09-03 1:33 ` Matthew Hall
2014-09-25 7:52 ` Zhan, Zhaochen [this message]
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=6D0EE020084B194084D70B0A8D2207B8ED8B26@SHSMSX104.ccr.corp.intel.com \
--to=zhaochen.zhan@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@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).