From: jspewock@iol.unh.edu
To: ci@dpdk.org
Cc: Jeremy Spewock <jspewock@iol.unh.edu>
Subject: [PATCH v7 0/4] Add ACVP Tool
Date: Mon, 3 Apr 2023 14:39:26 -0400 [thread overview]
Message-ID: <20230403183930.12001-2-jspewock@iol.unh.edu> (raw)
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: https://mails.dpdk.org/archives/ci/2023-March/002112.html
v6: https://mails.dpdk.org/archives/ci/2023-March/002147.html
v7:
* fix commit messages
* fix whitespace errors
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 | 118 +++++++++++++
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, 496 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
--
2.40.0
next reply other threads:[~2023-04-03 18:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 18:39 jspewock [this message]
2023-04-03 18:39 ` [PATCH v7 1/4] tools: add acvp_tool jspewock
2023-04-03 18:39 ` [PATCH v7 2/4] tools: add default config file for acvp_tool jspewock
2023-04-03 18:39 ` [PATCH v7 3/4] tools: add requirements " jspewock
2023-04-03 18:39 ` [PATCH v7 4/4] doc: add readme " jspewock
2023-04-04 13:20 ` [PATCH v7 0/4] Add ACVP Tool Ali Alnubani
2023-04-10 14:56 ` Patrick Robb
2023-04-10 15:19 ` Ali Alnubani
2023-04-11 21:22 ` Patrick Robb
2023-04-12 8:16 ` Thomas Monjalon
2023-04-12 21:10 ` Jeremy Spewock
2023-04-13 21:20 ` Aaron Conole
2023-04-13 21:20 ` Aaron Conole
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=20230403183930.12001-2-jspewock@iol.unh.edu \
--to=jspewock@iol.unh.edu \
--cc=ci@dpdk.org \
/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).