DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Eli Britstein <elibr@nvidia.com>, <dev@dpdk.org>
Cc: <xiaoyun.li@intel.com>, Matan Azrad <matan@nvidia.com>,
	Shahaf Shuler <shahafs@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	"Gregory Etelson" <getelson@nvidia.com>, <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH V2 2/2] net/mlx5: add support for more tunnel types
Date: Tue, 19 Oct 2021 22:52:11 +0100	[thread overview]
Message-ID: <2c2604b2-1b5a-c23e-0202-08fe1eab58bd@intel.com> (raw)
In-Reply-To: <20210923084301.5139-2-elibr@nvidia.com>

On 9/23/2021 9:43 AM, Eli Britstein wrote:
> Accept RTE_FLOW_ITEM_TYPE_GRE, RTE_FLOW_ITEM_TYPE_NVGRE and
> RTE_FLOW_ITEM_TYPE_GENEVE as valid tunnel types.
> 
> Fixes: 4ec6360de37d ("net/mlx5: implement tunnel offload")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Eli Britstein <elibr@nvidia.com>

Moving ack form first version of the set for record:

Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>



  reply	other threads:[~2021-10-19 21:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 14:25 [dpdk-dev] [PATCH 1/2] app/testpmd: add " Eli Britstein
2021-09-13 14:25 ` [dpdk-dev] [PATCH 2/2] net/mlx5: add support for more " Eli Britstein
2021-10-18  8:48   ` Slava Ovsiienko
2021-09-20 15:57 ` [dpdk-dev] [PATCH 1/2] app/testpmd: add " Ferruh Yigit
2021-09-23  8:43   ` [dpdk-dev] [PATCH V2 " Eli Britstein
2021-09-23  8:43     ` [dpdk-dev] [PATCH V2 2/2] net/mlx5: add support for more " Eli Britstein
2021-10-19 21:52       ` Ferruh Yigit [this message]
2021-10-14 17:15     ` [dpdk-dev] [PATCH V2 1/2] app/testpmd: add " Ferruh Yigit
2021-10-14 18:29     ` Gregory Etelson
2021-10-19 21:52       ` Ferruh Yigit

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=2c2604b2-1b5a-c23e-0202-08fe1eab58bd@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=elibr@nvidia.com \
    --cc=getelson@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=shahafs@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).