From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/3] ACL: Fix bug in acl_merge_trie() and add a new test-case for it to the UT
Date: Fri, 22 May 2015 18:48:48 +0100 [thread overview]
Message-ID: <1432316931-18406-1-git-send-email-konstantin.ananyev@intel.com> (raw)
ACL: fix a problem in acl_merge_trie
ACL: add new test case for ranges build
ACL: remove subtree_id calculations at build stage
app/test/test_acl.c | 147 +++++++++++++++++++++++++++++++++++++++++++++--
lib/librte_acl/acl.h | 7 ---
lib/librte_acl/acl_bld.c | 121 ++++----------------------------------
3 files changed, 155 insertions(+), 120 deletions(-)
--
1.8.5.3
next reply other threads:[~2015-05-22 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 17:48 Konstantin Ananyev [this message]
2015-05-22 17:48 ` [dpdk-dev] [PATCH 1/3] ACL: fix a problem in acl_merge_trie Konstantin Ananyev
2015-05-22 17:48 ` [dpdk-dev] [PATCH 2/3] ACL: add new test case for ranges build Konstantin Ananyev
2015-05-22 17:48 ` [dpdk-dev] [PATCH 3/3] ACL: remove subtree_id calculations at build stage Konstantin Ananyev
2015-06-02 20:56 ` Thomas Monjalon
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=1432316931-18406-1-git-send-email-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@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).