From: Srujana Challa <schalla@marvell.com>
To: <gakhil@marvell.com>
Cc: <dev@dpdk.org>, <jerinj@marvell.com>, <hemant.agrawal@nxp.com>
Subject: [PATCH v1] Revert "doc: extension of crypto event callback announced"
Date: Thu, 1 Aug 2024 13:06:07 +0530 [thread overview]
Message-ID: <20240801073607.3026414-1-schalla@marvell.com> (raw)
In-Reply-To: <20240801071147.3020911-1-schalla@marvell.com>
The previously planned update to the `rte_cryptodev_cb_fn` function
prototype is being reverted. The introduction of the
`rte_cryptodev_queue_pair_event_error_query` API provides a means for
applications to retrieve the queue pair ID that encountered an error
interrupt. This makes the addition of the `qp_id` parameter to the
`rte_cryptodev_cb_fn` function unnecessary, and as such, the proposed
extension is no longer required.
Signed-off-by: Srujana Challa <schalla@marvell.com>
---
doc/guides/rel_notes/deprecation.rst | 5 -----
1 file changed, 5 deletions(-)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 211f59fdc9..4dd592c371 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -169,11 +169,6 @@ Deprecation Notices
* fib: A new flag field will be introduced in ``rte_fib_conf`` structure
in DPDK 24.11. This field will be used to pass extra configuration settings.
-* cryptodev: The function ``rte_cryptodev_cb_fn`` will be updated
- to have another parameter ``qp_id`` to return the queue pair ID
- which got error interrupt to the application,
- so that application can reset that particular queue pair.
-
* cryptodev: The structure ``rte_cryptodev_qp_conf`` will be updated
to have a new parameter to set priority of that particular queue pair.
--
2.25.1
next prev parent reply other threads:[~2024-08-01 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-01 7:11 [PATCH] " Srujana Challa
2024-08-01 7:36 ` Srujana Challa [this message]
2024-10-07 17:31 ` [PATCH v1] " Stephen Hemminger
2024-10-09 19:46 ` [EXTERNAL] " Akhil Goyal
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=20240801073607.3026414-1-schalla@marvell.com \
--to=schalla@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
/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).