From: Dekel Peled <dekelp@mellanox.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "jerinjacobk@gmail.com" <jerinjacobk@gmail.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"olivier.matz@6wind.com" <olivier.matz@6wind.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
Asaf Penso <asafp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce change in IPv6 item struct
Date: Tue, 4 Aug 2020 13:17:52 +0000 [thread overview]
Message-ID: <VI1PR05MB53908D24FF604F4FE2FA49ABB64A0@VI1PR05MB5390.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <678a4cdeb67c9873c9d2842ec5a747f35600399f.1596483829.git.dekelp@mellanox.com>
Kind reminder to all maintainers, please review and ack/comment.
> -----Original Message-----
> From: Dekel Peled <dekelp@mellanox.com>
> Sent: Monday, August 3, 2020 10:51 PM
> To: dev@dpdk.org
> Cc: jerinjacobk@gmail.com; stephen@networkplumber.org;
> arybchenko@solarflare.com; ajit.khaparde@broadcom.com;
> maxime.coquelin@redhat.com; olivier.matz@6wind.com;
> david.marchand@redhat.com; ferruh.yigit@intel.com
> Subject: [PATCH] doc: announce change in IPv6 item struct
>
> Struct rte_flow_item_ipv6 will be modified to include additional values,
> indicating existence or absence of IPv6 extension headers following the IPv6
> header, as proposed in RFC https://mails.dpdk.org/archives/dev/2020-
> August/177257.html.
> Because of ABI break this change is proposed for 20.11.
>
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index ea4cfa7..5201142 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -110,6 +110,11 @@ Deprecation Notices
> break the ABI checks, that is why change is planned for 20.11.
> The list of internal APIs are mainly ones listed in ``rte_ethdev_driver.h``.
>
> +* ethdev: The ``struct rte_flow_item_ipv6`` struct will be modified to
> +include
> + additional values, indicating existence or absence of IPv6 extension
> +headers
> + following the IPv6 header, as proposed in RFC
> + https://mails.dpdk.org/archives/dev/2020-August/177257.html.
> +
> * traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly
> made
> ABI stable in the v19.11 release. The TM maintainer and other contributors
> have
> agreed to keep the TM APIs as experimental in expectation of additional
> spec
> --
> 1.8.3.1
next prev parent reply other threads:[~2020-08-04 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 19:51 Dekel Peled
2020-08-04 13:17 ` Dekel Peled [this message]
2020-08-06 17:09 ` Ori Kam
2020-08-06 12:30 ` Thomas Monjalon
2020-08-06 15:48 ` Ajit Khaparde
2020-08-06 22:22 ` Thomas Monjalon
2020-08-06 15:10 ` Andrew Rybchenko
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=VI1PR05MB53908D24FF604F4FE2FA49ABB64A0@VI1PR05MB5390.eurprd05.prod.outlook.com \
--to=dekelp@mellanox.com \
--cc=ajit.khaparde@broadcom.com \
--cc=arybchenko@solarflare.com \
--cc=asafp@mellanox.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.org \
/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).