From: Raslan Darawsheh <rasland@nvidia.com>
To: Shiri Kuzin <shirik@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: update GENEVE TLV option exist bit
Date: Sun, 6 Jun 2021 11:32:12 +0000 [thread overview]
Message-ID: <DM4PR12MB5054B44B022B341B8BF71D0FCF399@DM4PR12MB5054.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210531114543.9881-1-shirik@nvidia.com>
Hi Shiri,
> -----Original Message-----
> From: Shiri Kuzin <shirik@nvidia.com>
> Sent: Monday, May 31, 2021 2:46 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH] net/mlx5: update GENEVE TLV option exist bit
>
> The GENEVE TLV option matching is done using a flex parser.
>
> Recent update in firmware, requires that in order to match on the GENEVE
> TLV option the "geneve_tlv_option_0_exist" bit should be set.
>
> Add the new "geneve_tlv_option_0_exist" setting when translating the
> GENEVE TLV option item.
>
> Signed-off-by: Shiri Kuzin <shirik@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
This is a valid Patch for Stable, so I'll add it during integration
Cc:stable@dpdk.org
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next parent reply other threads:[~2021-06-06 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210531114543.9881-1-shirik@nvidia.com>
2021-06-06 11:32 ` Raslan Darawsheh [this message]
2021-06-24 8:55 ` Shiri Kuzin
2021-06-24 11:20 ` Raslan Darawsheh
2021-08-22 10:47 ` Raslan Darawsheh
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=DM4PR12MB5054B44B022B341B8BF71D0FCF399@DM4PR12MB5054.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=shirik@nvidia.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@nvidia.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).