From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Michael Qiu <qiudayu@chinac.com>
Cc: dev@dpdk.org, "Tan, Jianfeng" <jianfeng.tan@intel.com>,
Michael Qiu <qdy220091330@gmail.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] examples/tep_term: Fix packet len for multi-seg mbuf
Date: Tue, 25 Oct 2016 17:53:23 +0200 [thread overview]
Message-ID: <2125737.gUPR0tuuya@xps13> (raw)
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E364E6C358A@SHSMSX103.ccr.corp.intel.com>
> > For multi-seg mbuf, ip->total_length should be pkt_len subtract
> > ether len.
> >
> > Fixes: 4abe471ed6fc("examples/tep_term: implement VXLAN processing")
> >
> > Signed-off-by: Michael Qiu <qiudayu@chinac.com>
>
> Acked-by: Jianfeng Tan <jianfeng.tan@intel.com>
Applied, thanks
next prev parent reply other threads:[~2016-10-25 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 5:49 [dpdk-dev] [PATCH 1/2] examples/tep_term: Fix l4_len issue Michael Qiu
2016-10-18 5:49 ` [dpdk-dev] [PATCH 2/2] examples/tep_term: Fix packet len for multi-seg mbuf Michael Qiu
2016-10-24 5:41 ` Tan, Jianfeng
2016-10-25 15:53 ` Thomas Monjalon [this message]
2016-10-24 5:41 ` [dpdk-dev] [PATCH 1/2] examples/tep_term: Fix l4_len issue Tan, Jianfeng
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=2125737.gUPR0tuuya@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jianfeng.tan@intel.com \
--cc=qdy220091330@gmail.com \
--cc=qiudayu@chinac.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).