From: Thomas Monjalon <thomas@monjalon.net>
To: Gavin Li <gavinl@nvidia.com>
Cc: matan@nvidia.com, viacheslavo@nvidia.com, orika@nvidia.com,
dev@dpdk.org, rasland@nvidia.com,
Ferruh Yigit <ferruh.yigit@amd.com>,
bruce.richardson@intel.com, jerinj@marvell.com,
ajit.khaparde@broadcom.com, maxime.coquelin@redhat.com,
stephen@networkplumber.org
Subject: Re: [V1] doc: announce deprecation of flow item VXLAN-GPE
Date: Mon, 29 Jul 2024 10:48:15 +0200 [thread overview]
Message-ID: <3264319.aV6nBDHxoP@thomas> (raw)
In-Reply-To: <28be443d-928e-4156-904a-dccb138a6e5f@amd.com>
26/07/2024 13:31, Ferruh Yigit:
> On 7/26/2024 9:51 AM, Gavin Li wrote:
> > Adding the deprecation notice as reminder for removing
> > RTE_FLOW_ITEM_TYPE_VXLAN_GPE and its related structures,
> > eg. rte_vxlan_gpe_hdr, rte_flow_item_vxlan_gpe, etc.
> >
> > The proposed time of the removal is DPDK release 25.11.
> >
> > Signed-off-by: Gavin Li <gavinl@nvidia.com>
> > ---
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > + * ethdev,net: The flow item ``RTE_FLOW_ITEM_TYPE_VXLAN_GPE`` is replaced with ``RTE_FLOW_ITEM_TYPE_VXLAN``.
> > + The struct ``rte_flow_item_vxlan_gpe``, its mask ``rte_flow_item_vxlan_gpe_mask`` are replaced with
> > + ``rte_flow_item_vxlan and its mask`` and its mask ``rte_flow_item_vxlan_mask``.
> > + The item ``RTE_FLOW_ITEM_TYPE_VXLAN_GPE``, the struct ``rte_flow_item_vxlan_gpe``, its mask ``rte_flow_item_vxlan_gpe_mask``,
> > + and the header struct ``rte_vxlan_gpe_hdr`` with the macro ``RTE_ETHER_VXLAN_GPE_HLEN``
> > + will be removed in DPDK 25.11.
>
> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Acked-by: Thomas Monjalon <thomas@monjalon.net>
next prev parent reply other threads:[~2024-07-29 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 8:51 Gavin Li
2024-07-26 11:31 ` Ferruh Yigit
2024-07-29 8:48 ` Thomas Monjalon [this message]
2024-07-29 13:47 ` Ajit Khaparde
2024-07-31 10:33 ` Thomas Monjalon
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=3264319.aV6nBDHxoP@thomas \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=gavinl@nvidia.com \
--cc=jerinj@marvell.com \
--cc=matan@nvidia.com \
--cc=maxime.coquelin@redhat.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=stephen@networkplumber.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).