test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhao, XinfengX" <xinfengx.zhao@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhao, XinfengX" <xinfengx.zhao@intel.com>
Subject: Re: [dts] [PATCH V1 0/3] add new test cases for aes-docsisbpi
Date: Mon, 1 Jun 2020 07:46:48 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC56902@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20200515080332.102832-1-xinfengx.zhao@intel.com>

Applied the series, thanks

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xinfengx
> Sent: Friday, May 15, 2020 4:03 PM
> To: dts@dpdk.org
> Cc: Zhao, XinfengX <xinfengx.zhao@intel.com>
> Subject: [dts] [PATCH V1 0/3] add new test cases for aes-docsisbpi
> 
> test_plans: add aes-docsisbpi algorithm into crypto_perf test plan
> tests: add test cases for aes-docsisbpi
> conf: add test setting for aes-docsisbpi cases
> 
>  conf/crypto_perf_cryptodev_perf.cfg           | 38 +++++++++++++++-
>  test_plans/crypto_perf_cryptodev_perf_test_plan.rst  |  4 ++
> tests/TestSuite_crypto_perf_cryptodev_perf.py | 44 +++++++++++++++++++
>  3 files changed, 85 insertions(+), 1 deletion(-)
> 
> --
> 2.17.1


      parent reply	other threads:[~2020-06-01  7:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  8:03 xinfengx
2020-05-15  8:03 ` [dts] [PATCH V1 1/3] test_plans: add aes-docsisbpi algorithm into crypto_perf test plan xinfengx
2020-05-15  8:03 ` [dts] [PATCH V1 2/3] tests: add test cases for aes-docsisbpi xinfengx
2020-05-15  8:03 ` [dts] [PATCH V1 3/3] conf: add test setting for aes-docsisbpi cases xinfengx
2020-05-27  8:07   ` Wan, Zhe
2020-05-26  7:45 ` [dts] [PATCH V1 0/3] add new test cases for aes-docsisbpi Zhao, XinfengX
2020-06-01  7:46 ` Tu, Lijuan [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=8CE3E05A3F976642AAB0F4675D0AD20E0BC56902@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=xinfengx.zhao@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).