From: <jerinj@marvell.com>
To: <dev@dpdk.org>, Ray Kinsella <mdr@ashroe.eu>,
Jerin Jacob <jerinj@marvell.com>,
Jay Jayatheerthan <jay.jayatheerthan@intel.com>,
"Pavan Nikhilesh" <pbhagavatula@marvell.com>,
Harman Kalra <hkalra@marvell.com>,
Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
Shijith Thotton <sthotton@marvell.com>
Cc: <thomas@monjalon.net>, <david.marchand@redhat.com>
Subject: [dpdk-dev] [PATCH] doc: remove deprecation notices for eventdev
Date: Tue, 2 Nov 2021 21:19:56 +0530 [thread overview]
Message-ID: <20211102154956.1443591-1-jerinj@marvell.com> (raw)
From: Jerin Jacob <jerinj@marvell.com>
All deprecation notice targeted for v21.11 of eventdev has been
committed in the following commits, remove deprecation notices.
Fixes: 3c838062b91 ("eventdev: introduce event vector Rx capability")
Fixes: 929ebdd5430 ("eventdev/eth_rx: simplify event vector config")
Fixes: 295c053f90f ("eventdev: hide event device related structures")
Fixes: dd451ad1520 ("doc: remove event crypto metadata deprecation note")
Signed-off-by: Jerin Jacob <jerinj@marvell.com>
---
doc/guides/rel_notes/deprecation.rst | 26 --------------------------
1 file changed, 26 deletions(-)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 4366015b01..b0ffc3be08 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -131,32 +131,6 @@ Deprecation Notices
pointer for the private data to the application which can be attached
to the packet while enqueuing.
-* eventdev: The file ``rte_eventdev_pmd.h`` will be renamed to ``eventdev_driver.h``
- to make the driver interface as internal and the structures ``rte_eventdev_data``,
- ``rte_eventdev`` and ``rte_eventdevs`` will be moved to a new file named
- ``rte_eventdev_core.h`` in DPDK 21.11.
- The ``rte_`` prefix for internal structures and functions will be removed across the
- library.
- The experimental eventdev trace APIs and ``rte_event_vector_pool_create``,
- ``rte_event_eth_rx_adapter_vector_limits_get`` will be promoted to stable.
- An 8-byte reserved field will be added to the structure ``rte_event_timer`` to
- support future extensions.
-
-* eventdev: The structure ``rte_event_eth_rx_adapter_queue_conf`` will be
- extended to include ``rte_event_eth_rx_adapter_event_vector_config`` elements
- and the function ``rte_event_eth_rx_adapter_queue_event_vector_config`` will
- be removed in DPDK 21.11.
-
- An application can enable event vectorization by passing the desired vector
- values to the function ``rte_event_eth_rx_adapter_queue_add`` using
- the structure ``rte_event_eth_rx_adapter_queue_add``.
-
-* eventdev: Reserved bytes of ``rte_event_crypto_request`` is a space holder
- for ``response_info``. Both should be decoupled for better clarity in
- DPDK 21.11.
- New space for ``response_info`` can be made by changing
- ``rte_event_crypto_metadata`` type to structure from union.
-
* metrics: The function ``rte_metrics_init`` will have a non-void return
in order to notify errors instead of calling ``rte_exit``.
--
2.33.1
next reply other threads:[~2021-11-02 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 15:49 jerinj [this message]
2021-11-02 16:01 ` Thomas Monjalon
2021-11-02 16:29 ` Jerin Jacob
2021-11-02 19:58 ` David Marchand
2021-11-04 13:54 ` Jerin Jacob
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=20211102154956.1443591-1-jerinj@marvell.com \
--to=jerinj@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=jay.jayatheerthan@intel.com \
--cc=mdr@ashroe.eu \
--cc=pbhagavatula@marvell.com \
--cc=sthotton@marvell.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;
as well as URLs for NNTP newsgroup(s).