From: Anoob Joseph <anoobj@marvell.com>
To: Aakash Sasidharan <asasidharan@marvell.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Shijith Thotton <sthotton@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Aakash Sasidharan <asasidharan@marvell.com>,
Abhinandan Gujjar <abhinandan.gujjar@intel.com>
Subject: RE: [PATCH 2/3] test/event_crypto_adapter: skip unsupported test
Date: Wed, 23 Aug 2023 04:01:40 +0000 [thread overview]
Message-ID: <PH0PR18MB467219277252E0E7135CBB8BDF1CA@PH0PR18MB4672.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230822131649.3509986-2-asasidharan@marvell.com>
>
> Skip the test if rte_event_crypto_adapter_caps_get()
> returns -ENOTSUP.
>
> Signed-off-by: Aakash Sasidharan <asasidharan@marvell.com>
> ---
> app/test/test_event_crypto_adapter.c | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
Acked-by: Anoob Joseph <anoobj@marvell.com>
next prev parent reply other threads:[~2023-08-23 4:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 13:16 [PATCH 1/3] event/cnxk: fix return values for capability API Aakash Sasidharan
2023-08-22 13:16 ` [PATCH 2/3] test/event_crypto_adapter: skip unsupported test Aakash Sasidharan
2023-08-23 4:01 ` Anoob Joseph [this message]
2023-08-23 4:33 ` Gujjar, Abhinandan S
2023-08-23 7:48 ` Aakash Sasidharan
2023-08-23 8:16 ` Aakash Sasidharan
2023-08-23 8:37 ` Gujjar, Abhinandan S
2023-08-22 13:16 ` [PATCH 3/3] test/event_crypto_adapter: fix crypto null dev creation Aakash Sasidharan
2023-08-23 4:00 ` Anoob Joseph
2023-08-23 4:48 ` Gujjar, Abhinandan S
2023-08-23 5:47 ` Anoob Joseph
2023-08-23 6:17 ` Gujjar, Abhinandan S
2023-08-23 14:20 ` Jerin Jacob
2023-08-23 3:59 ` [PATCH 1/3] event/cnxk: fix return values for capability API Anoob Joseph
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=PH0PR18MB467219277252E0E7135CBB8BDF1CA@PH0PR18MB4672.namprd18.prod.outlook.com \
--to=anoobj@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=asasidharan@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=sthotton@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).