DPDK patches and discussions
 help / color / mirror / Atom feed
From: Volodymyr Fialko <vfialko@marvell.com>
To: <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
	Volodymyr Fialko <vfialko@marvell.com>,
	Akhil Goyal <gakhil@marvell.com>
Cc: <anoobj@marvell.com>
Subject: [PATCH] build: fix missing crypto vec limits in version
Date: Tue, 6 Dec 2022 10:23:29 +0100	[thread overview]
Message-ID: <20221206092329.2250774-1-vfialko@marvell.com> (raw)

Add missing function `rte_event_crypto_adapter_vector_limits_get` to
version.map.

Fixes: c1749bc5ee10 ("eventdev: introduce event cryptodev vector type")

Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
---
 lib/eventdev/version.map | 1 +
 1 file changed, 1 insertion(+)

diff --git a/lib/eventdev/version.map b/lib/eventdev/version.map
index dd63ec6f68..1a7fffd17f 100644
--- a/lib/eventdev/version.map
+++ b/lib/eventdev/version.map
@@ -20,6 +20,7 @@ DPDK_23 {
 	rte_event_crypto_adapter_stats_get;
 	rte_event_crypto_adapter_stats_reset;
 	rte_event_crypto_adapter_stop;
+	rte_event_crypto_adapter_vector_limits_get;
 	rte_event_dequeue_timeout_ticks;
 	rte_event_dev_attr_get;
 	rte_event_dev_close;
-- 
2.25.1


             reply	other threads:[~2022-12-06  9:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  9:23 Volodymyr Fialko [this message]
2022-12-06  9:28 ` Zhang, Fan
2023-01-17 16:25   ` Jerin Jacob
2023-01-17 21:10     ` Thomas Monjalon
2023-01-18 10:21 ` [PATCH v2] eventdev/crypto: fix missing crypto vec limits Volodymyr Fialko
2023-01-23  9:35   ` Gujjar, Abhinandan S
2023-01-23 13:26     ` 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=20221206092329.2250774-1-vfialko@marvell.com \
    --to=vfialko@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.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).