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, jerinj@marvell.com,
	arybchenko@solarflare.com, ferruh.yigit@intel.com,
	bruce.richardson@intel.com, hemant.agrawal@nxp.com,
	stephen@networkplumber.org, ajit.khaparde@broadcom.com,
	johndale@cisco.com, xavier.huwei@huawei.com,
	xuanziyang2@huawei.com, wei.zhao1@intel.com, rmody@marvell.com
Subject: [dpdk-dev] [PATCH] doc: announce removal of legacy ethdev filtering API
Date: Mon,  3 Aug 2020 13:49:01 +0200	[thread overview]
Message-ID: <20200803114901.3251051-1-thomas@monjalon.net> (raw)

Deprecation of rte_eth_dev_filter_ctrl() was announced in 2016,
and confirmed last year by avoiding include of rte_eth_ctrl.h.
After 4 years, it is time to complete the removal of the API
which is replaced with rte_flow.

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

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index ea4cfa7a48..6e12e57a13 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -81,8 +81,7 @@ Deprecation Notices
   HASH and L2_TUNNEL, is superseded by the generic flow API (rte_flow) in
   PMDs that implement the latter.
-  Target release for removal of the legacy API will be defined once most
-  PMDs have switched to rte_flow.
+  The legacy API 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.

             reply	other threads:[~2020-08-03 11:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-03 11:49 Thomas Monjalon [this message]
2020-08-03 11:54 ` Andrew Rybchenko
2020-08-03 11:57   ` Jerin Jacob
2020-08-03 14:30     ` Ajit Khaparde
2020-08-06  0:26       ` Thomas Monjalon
2020-08-04  7:51 ` David Marchand

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=20200803114901.3251051-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=adrien.mazarguil@6wind.com \
    --cc=ajit.khaparde@broadcom.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=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=johndale@cisco.com \
    --cc=rmody@marvell.com \
    --cc=shahafs@mellanox.com \
    --cc=stephen@networkplumber.org \
    --cc=wei.zhao1@intel.com \
    --cc=xavier.huwei@huawei.com \
    --cc=xuanziyang2@huawei.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).