From: Aaron Conole <aconole@redhat.com>
To: jspewock@iol.unh.edu
Cc: ci@dpdk.org
Subject: Re: [PATCH v5 0/4] Add ACVP tool
Date: Fri, 24 Mar 2023 09:34:19 -0400 [thread overview]
Message-ID: <f7tbkkip92c.fsf@redhat.com> (raw)
In-Reply-To: <20230315172837.29736-1-jspewock@iol.unh.edu> (jspewock@iol.unh.edu's message of "Wed, 15 Mar 2023 13:28:34 -0400")
jspewock@iol.unh.edu writes:
> From: Jeremy Spewock <jspewock@iol.unh.edu>
>
> v1: https://mails.dpdk.org/archives/ci/2022-January/001599.html
> v2: https://mails.dpdk.org/archives/ci/2022-January/001611.html
> v3: https://mails.dpdk.org/archives/ci/2022-February/001636.html
> v4: https://mails.dpdk.org/archives/ci/2022-April/001702.html
> v5:
> * updated out-of-date readme to better match current implementation
> * updated default config file to support more algorithms
Just one nit that I sent. Overall, LGTM.
> Brandon Lo (4):
> tools: add acvp_tool
> tools: add default config file for acvp_tool
> tools: add requirements file for acvp_tool
> doc: add readme file for acvp_tool
>
> tools/acvp/README | 129 +++++++++++++++
> tools/acvp/__init__.py | 0
> tools/acvp/acvp_config.json | 52 ++++++
> tools/acvp/acvp_tool.py | 319 ++++++++++++++++++++++++++++++++++++
> tools/acvp/requirements.txt | 7 +
> 5 files changed, 507 insertions(+)
> create mode 100644 tools/acvp/README
> create mode 100644 tools/acvp/__init__.py
> create mode 100644 tools/acvp/acvp_config.json
> create mode 100755 tools/acvp/acvp_tool.py
> create mode 100644 tools/acvp/requirements.txt
prev parent reply other threads:[~2023-03-24 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 17:28 jspewock
2023-03-15 17:28 ` [PATCH v5 1/4] tools: add acvp_tool jspewock
2023-03-15 17:28 ` [PATCH v5 2/4] tools: add default config file for acvp_tool jspewock
2023-03-15 17:28 ` [PATCH v5 3/4] tools: add requirements " jspewock
2023-03-15 17:28 ` [PATCH v5 4/4] doc: add readme " jspewock
2023-03-24 13:34 ` Aaron Conole
2023-03-23 13:54 ` [PATCH v5 0/4] Add ACVP tool Patrick Robb
2023-03-24 13:34 ` Aaron Conole [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=f7tbkkip92c.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=jspewock@iol.unh.edu \
/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).