From: Akhil Goyal <gakhil@marvell.com>
To: Stanislaw Kardach <kda@semihalf.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: "upstream@semihalf.com" <upstream@semihalf.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] [PATCH] test/ipsec: check for cryptodevs before testing
Date: Tue, 21 Jun 2022 13:10:31 +0000 [thread overview]
Message-ID: <CO6PR18MB44840F658DF3EBAB5E4262BED8B39@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220601110017.400040-1-kda@semihalf.com>
> Make sure that ipsec_perf_autotest checks if there are any crypto
> devices available before it starts performance testing.
> Same test is performed in the ipsec_autotest so it seems prudent to do
> it here too to not introduce false failures.
>
> Signed-off-by: Stanislaw Kardach <kda@semihalf.com>
> ---
Acked-by: Akhil Goyal <gakhil@marvell.com>
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2022-06-21 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 11:00 Stanislaw Kardach
2022-06-21 13:10 ` Akhil Goyal [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=CO6PR18MB44840F658DF3EBAB5E4262BED8B39@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=kda@semihalf.com \
--cc=konstantin.ananyev@intel.com \
--cc=upstream@semihalf.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).