From: Xueming Li <xuemingl@nvidia.com>
To: <dev@dpdk.org>
Cc: <xuemingl@nvidia.com>, Ferruh Yigit <ferruh.yigit@intel.com>,
Ray Kinsella <mdr@ashroe.eu>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"Ajit Khaparde" <ajit.khaparde@broadcom.com>
Subject: [dpdk-dev] [PATCH v2] ethdev: fix deprecation notice for shared Rx queue
Date: Tue, 2 Nov 2021 19:42:20 +0800 [thread overview]
Message-ID: <20211102114220.1332095-1-xuemingl@nvidia.com> (raw)
In-Reply-To: <20211102092911.1323554-1-xuemingl@nvidia.com>
Shared Rx queue feature has been supported, remove deprecation notice.
Fixes: dd22740cc291 ("ethdev: introduce shared Rx queue")
Signed-off-by: Xueming Li <xuemingl@nvidia.com>
---
doc/guides/rel_notes/deprecation.rst | 3 ---
1 file changed, 3 deletions(-)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 4366015b015..a708ad76912 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -90,9 +90,6 @@ Deprecation Notices
In v21.11 LTS, protocol header fields will be cleaned and only protocol header
struct will remain.
-* ethdev: Add new Rx queue offload flag ``RTE_ETH_RX_OFFLOAD_SHARED_RXQ`` and
- ``shared_group`` field to ``struct rte_eth_rxconf``.
-
* ethdev: Queue specific stats fields will be removed from ``struct rte_eth_stats``.
Mentioned fields are: ``q_ipackets``, ``q_opackets``, ``q_ibytes``, ``q_obytes``,
``q_errors``.
--
2.33.0
next prev parent reply other threads:[~2021-11-02 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 9:29 [dpdk-dev] [PATCH v1] ethdev: remove " Xueming Li
2021-11-02 10:10 ` Ferruh Yigit
2021-11-02 11:42 ` Xueming Li [this message]
2021-11-02 13:36 ` [dpdk-dev] [PATCH v2] ethdev: fix " Ferruh Yigit
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=20211102114220.1332095-1-xuemingl@nvidia.com \
--to=xuemingl@nvidia.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=mdr@ashroe.eu \
/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).