All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Gregory Etelson <getelson@nvidia.com>
Cc: dev@dpdk.org, stable@dpdk.org, matan@nvidia.com,
	rasland@nvidia.com, stable@dpdk.org,
	Aman Singh <aman.deep.singh@intel.com>,
	Xiaoyun Li <xiaoyun.li@intel.com>,
	Yuying Zhang <yuying.zhang@intel.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Ting Xu <ting.xu@intel.com>
Subject: Re: [PATCH v2] app/testpmd: fix GTP header parsing in csum FWD engine
Date: Mon, 14 Mar 2022 21:49:50 +0100	[thread overview]
Message-ID: <13394630.RDIVbhacDa@thomas> (raw)
In-Reply-To: <20220313090124.3028-1-getelson@nvidia.com>

13/03/2022 10:01, Gregory Etelson:
> GTP header can be followed by an optional 32 bits extension.
> GTP notifies about the extension presence through the E, S or PN
> header bits.
> 
> Csum GTP header parser did not check the extension bits value.
> 
> The patch updates GTP header length if at-least one of the
> extension bits is set.
> 
> Cc: stable@dpdk.org
> 
> Fixes: d8e5e69f3a9b ("app/testpmd: add GTP parsing and Tx checksum offload")
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Aman Singh <aman.deep.singh@intel.com>

It should be "Fixes" line, "Cc" line, blank line, and "Signed-off/Ack" lines.
Applied, thanks.



      reply	other threads:[~2022-03-14 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 14:20 [PATCH] app/testpmd: fix GTP header parsing in csum FWD engine Gregory Etelson
2022-03-11 13:34 ` Singh, Aman Deep
2022-03-13  8:44   ` Gregory Etelson
2022-03-13  9:01 ` [PATCH v2] " Gregory Etelson
2022-03-14 20:49   ` Thomas Monjalon [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=13394630.RDIVbhacDa@thomas \
    --to=thomas@monjalon.net \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=getelson@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=ting.xu@intel.com \
    --cc=xiaoyun.li@intel.com \
    --cc=yuying.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.