From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Slava Ovsiienko <viacheslavo@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>, Ori Kam <orika@nvidia.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Xiaoyun Li <xiaoyun.li@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix gtp psc extension header length
Date: Tue, 16 Nov 2021 14:27:30 +0000 [thread overview]
Message-ID: <aaf69b34-c8a1-af74-0f56-c95e40998eb3@intel.com> (raw)
In-Reply-To: <DM6PR12MB3753A0D26A02D02C9297C739DF999@DM6PR12MB3753.namprd12.prod.outlook.com>
On 11/16/2021 1:42 PM, Slava Ovsiienko wrote:
>> -----Original Message-----
>> From: Ferruh Yigit <ferruh.yigit@intel.com>
>> Sent: Monday, November 15, 2021 21:02
>> To: Raslan Darawsheh <rasland@nvidia.com>; Ori Kam <orika@nvidia.com>;
>> Slava Ovsiienko <viacheslavo@nvidia.com>
>> Cc: stable@dpdk.org; Xiaoyun Li <xiaoyun.li@intel.com>; dev@dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix gtp psc extension header
>> length
>>
>> On 11/4/2021 9:40 AM, Raslan Darawsheh wrote:
>>> Current implementation for raw encap sets the length to be in bytes,
>>> but, GTP 'extension' header length is an 8-bit field in 4-octet units.
>>>
>>> This fixes the length calculation of the header length.
>>>
>>> Fixes: 9213c50e36fa ("app/testpmd: support GTP PSC option in raw
>>> sets")
>>> Cc: viacheslavo@nvidia.com
>>> Cc: stable@dpdk.org
>>>
>>> Signed-off-by: Raslan Darawsheh <rasland@nvidia.com>
>
>
> Reviewed-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-11-16 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 9:35 [dpdk-stable] [PATCH] app/testpmd: fix gtp psc extention " Raslan Darawsheh
2021-11-04 9:40 ` [dpdk-stable] [PATCH v2] app/testpmd: fix gtp psc extension " Raslan Darawsheh
2021-11-15 19:02 ` [dpdk-dev] " Ferruh Yigit
2021-11-16 13:42 ` Slava Ovsiienko
2021-11-16 14:27 ` Ferruh Yigit [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=aaf69b34-c8a1-af74-0f56-c95e40998eb3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.com \
--cc=xiaoyun.li@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).