From: Anoob Joseph <anoobj@marvell.com>
To: Akhil Goyal <gakhil@marvell.com>, Thomas Monjalon <thomas@monjalon.net>
Cc: Jerin Jacob <jerinj@marvell.com>, <dev@dpdk.org>
Subject: [PATCH] cryptodev: add missing doc
Date: Thu, 7 Sep 2023 18:30:37 +0530 [thread overview]
Message-ID: <20230907130037.208-1-anoobj@marvell.com> (raw)
Description for rte_cryptodev_get_sec_ctx is missing. Add the same.
Signed-off-by: Anoob Joseph <anoobj@marvell.com>
---
lib/cryptodev/rte_cryptodev.h | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/lib/cryptodev/rte_cryptodev.h b/lib/cryptodev/rte_cryptodev.h
index ba730373fb..8876e0427f 100644
--- a/lib/cryptodev/rte_cryptodev.h
+++ b/lib/cryptodev/rte_cryptodev.h
@@ -973,6 +973,15 @@ struct rte_cryptodev_cb_rcu {
/**< RCU QSBR variable per queue pair */
};
+/**
+ * Get the security context for the cryptodev.
+ *
+ * @param dev_id
+ * The device identifier.
+ * @return
+ * - NULL on error.
+ * - Pointer to security context on success.
+ */
void *
rte_cryptodev_get_sec_ctx(uint8_t dev_id);
--
2.25.1
next reply other threads:[~2023-09-07 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 13:00 Anoob Joseph [this message]
2023-09-11 10:15 ` Thomas Monjalon
2023-09-12 10:42 ` [PATCH v2] " Anoob Joseph
2023-09-19 5:59 ` 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=20230907130037.208-1-anoobj@marvell.com \
--to=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@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).