From: "Zhang, Fan" <fanzhang.oss@gmail.com>
To: Aakash Sasidharan <asasidharan@marvell.com>,
Akhil Goyal <gakhil@marvell.com>
Cc: jerinj@marvell.com, anoobj@marvell.com, dev@dpdk.org, "Ji,
Kai" <kai.ji@intel.com>
Subject: Re: [PATCH] test/crypto: add cryptodev reconfig test
Date: Tue, 18 Apr 2023 14:29:30 +0100 [thread overview]
Message-ID: <87223cc1-d91b-7335-e783-a63182c6508f@gmail.com> (raw)
In-Reply-To: <20230405074117.2212923-1-asasidharan@marvell.com>
On 4/5/2023 8:41 AM, Aakash Sasidharan wrote:
> Add cryptodev tests to verify that the device supports
> reconfiguration any number of times via
> rte_cryptodev_configure API.
>
> Signed-off-by: Aakash Sasidharan <asasidharan@marvell.com>
> ---
Acked-by: Fan Zhang <fanzhang.oss@gmail.com>
next prev parent reply other threads:[~2023-04-18 13:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 7:41 Aakash Sasidharan
2023-04-06 14:21 ` Zhang, Fan
2023-04-10 7:19 ` [EXT] " Anoob Joseph
2023-04-18 13:29 ` Zhang, Fan [this message]
2023-04-19 13:37 ` O'Donovan, Saoirse
2023-05-03 7:13 ` 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=87223cc1-d91b-7335-e783-a63182c6508f@gmail.com \
--to=fanzhang.oss@gmail.com \
--cc=anoobj@marvell.com \
--cc=asasidharan@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=jerinj@marvell.com \
--cc=kai.ji@intel.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).