From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: roy.fan.zhang@intel.com
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/4]librte_port: modify macros to access packet meta-data
Date: Mon, 19 Oct 2015 16:59:31 +0200 [thread overview]
Message-ID: <6444334.trQLVujQca@xps13> (raw)
In-Reply-To: <1441978548-3582-1-git-send-email-roy.fan.zhang@intel.com>
2015-09-11 14:35, roy.fan.zhang@intel.com:
> app/test-pipeline/main.h | 2 ++
> app/test-pipeline/pipeline_hash.c | 34 ++++++++++++++-------------
> app/test-pipeline/pipeline_lpm.c | 2 +-
> app/test-pipeline/pipeline_lpm_ipv6.c | 2 +-
> app/test/test_table.h | 8 +++++--
> app/test/test_table_combined.c | 28 +++++++++++-----------
> app/test/test_table_pipeline.c | 3 ++-
> app/test/test_table_tables.c | 44 ++++++++++++++++++-----------------
> doc/guides/rel_notes/deprecation.rst | 5 ----
> doc/guides/rel_notes/release_2_2.rst | 4 +++-
> lib/librte_port/Makefile | 2 +-
> lib/librte_port/rte_port.h | 2 +-
examples/ip_pipeline does not need to be updated?
next prev parent reply other threads:[~2015-10-19 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 13:35 [PATCH 0/4]librte_port: modify macros to access packet meta-data roy.fan.zhang
2015-09-11 13:35 ` [PATCH 1/4] librte_port: " roy.fan.zhang
2015-09-11 13:35 ` [PATCH 2/4] app/test: modify table and pipeline test roy.fan.zhang
2015-09-11 13:35 ` [PATCH 3/4] app/test_pipeline: modify " roy.fan.zhang
2015-09-11 13:35 ` [PATCH 4/4] librte_port: modify release notes and deprecation notice roy.fan.zhang
2015-10-19 14:21 ` Thomas Monjalon
2015-09-11 13:40 ` [PATCH 0/4]librte_port: modify macros to access packet meta-data Dumitrescu, Cristian
2015-10-19 15:02 ` Thomas Monjalon
2015-10-19 14:59 ` Thomas Monjalon [this message]
2015-10-20 14:56 ` Dumitrescu, Cristian
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=6444334.trQLVujQca@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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).