DPDK CI discussions
 help / color / mirror / Atom feed
From: Ali Alnubani <alialnu@nvidia.com>
To: Brandon Lo <blo@iol.unh.edu>,
	"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "ci@dpdk.org" <ci@dpdk.org>
Subject: RE: [PATCH v3 0/4] Add ACVP tool
Date: Sat, 16 Apr 2022 10:35:36 +0000	[thread overview]
Message-ID: <DM4PR12MB5167A576DA025DC7AC358FD0DAF19@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220202150445.28995-1-blo@iol.unh.edu>

> -----Original Message-----
> From: Brandon Lo <blo@iol.unh.edu>
> Sent: Wednesday, February 2, 2022 5:05 PM
> To: NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>
> Cc: ci@dpdk.org; Brandon Lo <blo@iol.unh.edu>
> Subject: [PATCH v3 0/4] Add ACVP tool
> 
> v3:
> * Remove extra requirements in root requirements file
> 
> v2:
> * Add SPDX and copyright line
> 
> This adds a tool for easy interaction with the ACVP API. It will
> handle downloading test vectors, uploading the result, and fetching
> the final verdict of those uploaded results.
> 
> 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           |  71 ++++++++
>  tools/acvp/__init__.py      |   0
>  tools/acvp/acvp_config.json |  23 +++
>  tools/acvp/acvp_tool.py     | 319
> ++++++++++++++++++++++++++++++++++++
>  tools/acvp/requirements.txt |   7 +
>  5 files changed, 420 insertions(+)
>  create mode 100644 tools/acvp/README
>  create mode 100644 tools/acvp/__init__.py
>  create mode 100644 tools/acvp/acvp_config.json
>  create mode 100644 tools/acvp/acvp_tool.py
>  create mode 100644 tools/acvp/requirements.txt
> 
> --
> 2.25.1

Acked-by: Ali Alnubani <alialnu@nvidia.com>

  parent reply	other threads:[~2022-04-16 10:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 18:16 [PATCH v2 " Brandon Lo
2022-01-26 18:16 ` [PATCH v2 1/4] tools: add acvp_tool Brandon Lo
2022-01-26 18:25   ` Brandon Lo
2022-01-26 18:56     ` [PATCH v3 " Brandon Lo
2022-01-26 18:16 ` [PATCH v2 2/4] tools: add default config file for acvp_tool Brandon Lo
2022-01-26 18:16 ` [PATCH v2 3/4] tools: add requirements " Brandon Lo
2022-01-26 18:16 ` [PATCH v2 4/4] doc: add readme " Brandon Lo
2022-02-02 15:04 ` [PATCH v3 0/4] Add ACVP tool Brandon Lo
2022-02-02 15:04   ` [PATCH v3 1/4] tools: add acvp_tool Brandon Lo
2022-04-16 10:34     ` Ali Alnubani
2022-02-02 15:04   ` [PATCH v3 2/4] tools: add default config file for acvp_tool Brandon Lo
2022-02-02 15:04   ` [PATCH v3 3/4] tools: add requirements " Brandon Lo
2022-02-02 15:04   ` [PATCH v3 4/4] doc: add readme " Brandon Lo
2022-02-17 14:27   ` [PATCH v3 0/4] Add ACVP tool Brandon Lo
2022-04-16 10:35   ` Ali Alnubani [this message]
2022-04-18 13:36   ` [PATCH v4 " Brandon Lo
2022-04-18 13:36     ` [PATCH v4 1/4] tools: add acvp_tool Brandon Lo
2022-04-18 13:36     ` [PATCH v4 2/4] tools: add default config file for acvp_tool Brandon Lo
2022-04-18 13:36     ` [PATCH v4 3/4] tools: add requirements " Brandon Lo
2022-04-18 13:36     ` [PATCH v4 4/4] doc: add readme " Brandon Lo

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=DM4PR12MB5167A576DA025DC7AC358FD0DAF19@DM4PR12MB5167.namprd12.prod.outlook.com \
    --to=alialnu@nvidia.com \
    --cc=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).