DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: adrien.mazarguil@6wind.com, shahafs@mellanox.com,
	david.marchand@redhat.com, arybchenko@solarflare.com,
	ferruh.yigit@intel.com, bruce.richardson@intel.com,
	stephen@networkplumber.org, wei.zhao1@intel.com
Subject: [dpdk-dev] [PATCH] doc: announce removal of L2 tunnel filtering API
Date: Mon,  3 Aug 2020 20:06:27 +0200	[thread overview]
Message-ID: <20200803180627.3292763-1-thomas@monjalon.net> (raw)

The functions for L2 tunnel were missed when marking the legacy
filtering API as deprecated. That's why a separate notice is done
to make clear that it will be removed as well in DPDK 20.11.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
 doc/guides/rel_notes/deprecation.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index ea4cfa7a48..cad2f777f2 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -84,6 +84,12 @@ Deprecation Notices
   Target release for removal of the legacy API will be defined once most
   PMDs have switched to rte_flow.
+* ethdev: the legacy L2 tunnel filtering API is deprecated as the rest of
+  the legacy filtering API.
+  The functions ``rte_eth_dev_l2_tunnel_eth_type_conf`` and
+  ``rte_eth_dev_l2_tunnel_offload_set`` which were not marked as deprecated,
+  will be removed in DPDK 20.11.
 * ethdev: Update API functions returning ``void`` to return ``int`` with
   negative errno values to indicate various error conditions (e.g.
   invalid port ID, unsupported operation, failed operation):

             reply	other threads:[~2020-08-03 18:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 18:06 Thomas Monjalon [this message]
2020-08-04  3:54 ` Ajit Khaparde
2020-08-04  7:51 ` David Marchand
2020-08-04  8:54   ` Jerin Jacob
2020-08-05  8:45     ` Andrew Rybchenko
2020-08-06  0:37       ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200803180627.3292763-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=adrien.mazarguil@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=shahafs@mellanox.com \
    --cc=stephen@networkplumber.org \
    --cc=wei.zhao1@intel.com \


* 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).