From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>
Cc: Volodymyr Fialko <vfialko@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
Akhil Goyal <gakhil@marvell.com>,
"anoobj@marvell.com" <anoobj@marvell.com>
Subject: Re: [PATCH v2] eventdev/crypto: fix missing crypto vec limits
Date: Mon, 23 Jan 2023 18:56:04 +0530 [thread overview]
Message-ID: <CALBAE1MweAwsFPSUVMaj76K4_KGngaExx7ZWpzozMo6ikX7pEw@mail.gmail.com> (raw)
In-Reply-To: <PH0PR11MB58329C7EB9BBAC619AB51690E8C89@PH0PR11MB5832.namprd11.prod.outlook.com>
On Mon, Jan 23, 2023 at 3:05 PM Gujjar, Abhinandan S
<abhinandan.gujjar@intel.com> wrote:
>
> Acked-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
Updated the git commit as follows and applied to
dpdk-next-net-eventdev/for-main. Thanks
eventdev/crypto: fix missing symbol in map file
>
> > -----Original Message-----
> > From: Volodymyr Fialko <vfialko@marvell.com>
> > Sent: Wednesday, January 18, 2023 11:22 AM
> > To: dev@dpdk.org; Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>;
> > Jerin Jacob <jerinj@marvell.com>; Akhil Goyal <gakhil@marvell.com>;
> > Volodymyr Fialko <vfialko@marvell.com>
> > Cc: anoobj@marvell.com
> > Subject: [PATCH v2] eventdev/crypto: fix missing crypto vec limits
> >
> > 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>
> > ---
> > v2:
> > - mark function as experimental
> >
> > lib/eventdev/rte_event_crypto_adapter.h | 4 ++++
> > lib/eventdev/version.map | 1 +
> > 2 files changed, 5 insertions(+)
> >
> > diff --git a/lib/eventdev/rte_event_crypto_adapter.h
> > b/lib/eventdev/rte_event_crypto_adapter.h
> > index 83d154a6ce..2a69290097 100644
> > --- a/lib/eventdev/rte_event_crypto_adapter.h
> > +++ b/lib/eventdev/rte_event_crypto_adapter.h
> > @@ -595,6 +595,9 @@ int
> > rte_event_crypto_adapter_event_port_get(uint8_t id, uint8_t
> > *event_port_id);
> >
> > /**
> > + * @warning
> > + * @b EXPERIMENTAL: this API may change without prior notice
> > + *
> > * Retrieve vector limits for a given event dev and crypto dev pair.
> > * @see rte_event_crypto_adapter_vector_limits
> > *
> > @@ -610,6 +613,7 @@ rte_event_crypto_adapter_event_port_get(uint8_t id,
> > uint8_t *event_port_id);
> > * - 0: Success.
> > * - <0: Error code on failure.
> > */
> > +__rte_experimental
> > int rte_event_crypto_adapter_vector_limits_get(
> > uint8_t dev_id, uint16_t cdev_id,
> > struct rte_event_crypto_adapter_vector_limits *limits); diff --git
> > a/lib/eventdev/version.map b/lib/eventdev/version.map index
> > dd63ec6f68..c155af6d50 100644
> > --- a/lib/eventdev/version.map
> > +++ b/lib/eventdev/version.map
> > @@ -110,6 +110,7 @@ EXPERIMENTAL {
> > rte_event_eth_rx_adapter_event_port_get;
> >
> > # added in 22.07
> > + rte_event_crypto_adapter_vector_limits_get;
> > rte_event_port_quiesce;
> > rte_event_queue_attr_set;
> >
> > --
> > 2.34.1
>
prev parent reply other threads:[~2023-01-23 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 9:23 [PATCH] build: fix missing crypto vec limits in version Volodymyr Fialko
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 [this message]
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=CALBAE1MweAwsFPSUVMaj76K4_KGngaExx7ZWpzozMo6ikX7pEw@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=abhinandan.gujjar@intel.com \
--cc=anoobj@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=vfialko@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).