DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Ori Kam <orika@nvidia.com>, Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: [PATCH 2/2] ethdev: remove deprecated shared flow action
Date: Tue,  1 Sep 2026 16:10:33 -0700	[thread overview]
Message-ID: <20260901231033.169368-2-stephen@networkplumber.org> (raw)
In-Reply-To: <20260901231033.169368-1-stephen@networkplumber.org>

RTE_FLOW_ACTION_TYPE_SHARED has been deprecated since 21.05 when it
was replaced by RTE_FLOW_ACTION_TYPE_INDIRECT. It has no remaining
users in the tree.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 cover-letter.txt                       | 12 ++++++++++++
 doc/guides/rel_notes/release_26_11.rst |  3 ++-
 lib/ethdev/rte_flow.h                  | 11 -----------
 3 files changed, 14 insertions(+), 12 deletions(-)
 create mode 100644 cover-letter.txt

diff --git a/cover-letter.txt b/cover-letter.txt
new file mode 100644
index 0000000000..ecbd3239e2
--- /dev/null
+++ b/cover-letter.txt
@@ -0,0 +1,12 @@
+The DPDK policy is that an experimental API should be promoted to
+stable after one or more releases. A large part of the ethdev API had
+been left marked experimental long past that point; the meter API, for
+example, has been experimental since 17.11 and is implemented by many
+drivers and used by applications as if it were already stable. This
+series promotes 119 ethdev symbols introduced in 24.11 or earlier whose
+prototypes have not changed since, along with the stale doxygen
+EXPERIMENTAL warnings on structures and inline functions. The patches
+are split by feature so that each can be dropped on its own.
+
+The trace point symbols are left experimental on purpose; trace
+infrastructure is intended to stay unstable.
diff --git a/doc/guides/rel_notes/release_26_11.rst b/doc/guides/rel_notes/release_26_11.rst
index 591718253d..7f278d4645 100644
--- a/doc/guides/rel_notes/release_26_11.rst
+++ b/doc/guides/rel_notes/release_26_11.rst
@@ -71,7 +71,8 @@ Removed Items
 * Removed deprecated symbols:
 
   * eal: ``__rte_packed``
-  * ethdev: ``rte_flow_copy``, ``struct rte_flow_desc``
+  * ethdev: ``rte_flow_copy``, ``struct rte_flow_desc``,
+    ``RTE_FLOW_ACTION_TYPE_SHARED``
   * fib: ``RTE_FIB6_IPV6_ADDR_SIZE``, ``RTE_FIB6_MAXDEPTH``
   * lpm: ``RTE_LPM6_IPV6_ADDR_SIZE``, ``RTE_LPM6_MAX_DEPTH``
   * net: ``RTE_IP_ICMP_ECHO_REPLY``, ``RTE_IP_ICMP_ECHO_REQUEST``
diff --git a/lib/ethdev/rte_flow.h b/lib/ethdev/rte_flow.h
index dcd1dbf03e..869cc9a26d 100644
--- a/lib/ethdev/rte_flow.h
+++ b/lib/ethdev/rte_flow.h
@@ -3059,17 +3059,6 @@ enum rte_flow_action_type {
 	 */
 	RTE_FLOW_ACTION_TYPE_SAMPLE,
 
-	/**
-	 * @deprecated
-	 * @see RTE_FLOW_ACTION_TYPE_INDIRECT
-	 *
-	 * Describe action shared across multiple flow rules.
-	 *
-	 * Allow multiple rules reference the same action by handle (see
-	 * struct rte_flow_shared_action).
-	 */
-	RTE_FLOW_ACTION_TYPE_SHARED,
-
 	/**
 	 * Modify a packet header field, tag, mark or metadata.
 	 *
-- 
2.53.0


      reply	other threads:[~2026-09-01 23:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-01 23:10 [PATCH 1/2] ethdev: remove deprecated flow copy API Stephen Hemminger
2026-09-01 23:10 ` Stephen Hemminger [this message]

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=20260901231033.169368-2-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.com \
    --cc=thomas@monjalon.net \
    /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