From: "Li, WenjieX A" <wenjiex.a.li@intel.com>
To: "Xiao, QimaiX" <qimaix.xiao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Xiao, QimaiX" <qimaix.xiao@intel.com>
Subject: Re: [dts] [PATCH V1] add module dependences info of inline_ipsec
Date: Wed, 22 May 2019 08:11:23 +0000 [thread overview]
Message-ID: <8688172CD5C0B74590FAE19D9579F94B536F304C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1558509965-61578-1-git-send-email-qimaix.xiao@intel.com>
Reviewed-by: Wenjie <wenjiex.a.li@intel.com>
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xiao,qimai
> Sent: Wednesday, May 22, 2019 3:26 PM
> To: dts@dpdk.org
> Cc: Xiao, QimaiX <qimaix.xiao@intel.com>
> Subject: [dts] [PATCH V1] add module dependences info of inline_ipsec
>
> add module dependences info of this case
>
> Signed-off-by: xiao,qimai <qimaix.xiao@intel.com>
> ---
> test_plans/inline_ipsec_test_plan.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/test_plans/inline_ipsec_test_plan.rst
> b/test_plans/inline_ipsec_test_plan.rst
> index 9bec8cc..c37b229 100644
> --- a/test_plans/inline_ipsec_test_plan.rst
> +++ b/test_plans/inline_ipsec_test_plan.rst
> @@ -97,6 +97,9 @@ different ports of the peer traffic generator.
> Bind two ports to vfio-pci.
> modprobe vfio-pci
>
> +This suite depend PyCryptodome,it provide authenticated encryption
> +modes(GCM) module dependences:cryptography (1.7.2), pycryptodome
> +(3.4.7), pycryptodomex (3.4.7), pycryptopp (0.6.0), scapy (2.3.3 or
> +later)
>
> Test Case: Inline cfg parsing
> =============================
> --
> 2.17.1
next prev parent reply other threads:[~2019-05-22 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 7:26 xiao,qimai
2019-05-22 8:11 ` Li, WenjieX A [this message]
2019-05-22 9:05 ` Lin, Xueqin
2019-05-29 2:21 ` Tu, Lijuan
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=8688172CD5C0B74590FAE19D9579F94B536F304C@SHSMSX103.ccr.corp.intel.com \
--to=wenjiex.a.li@intel.com \
--cc=dts@dpdk.org \
--cc=qimaix.xiao@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).