From: Ali Alnubani <alialnu@nvidia.com>
To: "jspewock@iol.unh.edu" <jspewock@iol.unh.edu>,
"ci@dpdk.org" <ci@dpdk.org>
Subject: RE: [PATCH v4 0/2] tools: add acvp_tool
Date: Wed, 15 Mar 2023 08:50:02 +0000 [thread overview]
Message-ID: <DM4PR12MB5167BCFAA93E2D39B149E42ADABF9@DM4PR12MB5167.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230314201818.19560-2-jspewock@iol.unh.edu>
> -----Original Message-----
> From: jspewock@iol.unh.edu <jspewock@iol.unh.edu>
> Sent: Tuesday, March 14, 2023 10:18 PM
> To: ci@dpdk.org
> Cc: Jeremy Spewock <jspewock@iol.unh.edu>
> Subject: [PATCH v4 0/2] tools: add acvp_tool
>
> 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:
> * update tooling and documentation to match current implementation
>
Hi Jeremy,
Branched already sent a v4 (https://mails.dpdk.org/archives/ci/2022-April/001702.html).
As the original patchset wasn't merged yet, a better approach should be to squash your changes into v4's commits, and then resend as v5 detailing the changes you made.
You can apply v4's patches and find their message-ids from this thread: https://inbox.dpdk.org/ci/20220418133610.10835-1-blo@iol.unh.edu/.
$ wget -O- https://inbox.dpdk.org/ci/20220418133610.10835-2-blo@iol.unh.edu/raw | git am
$ wget -O- https://inbox.dpdk.org/ci/20220418133610.10835-3-blo@iol.unh.edu/raw | git am
$ wget -O- https://inbox.dpdk.org/ci/20220418133610.10835-4-blo@iol.unh.edu/raw | git am
$ wget -O- https://inbox.dpdk.org/ci/20220418133610.10835-5-blo@iol.unh.edu/raw | git am
Regards,
Ali
next prev parent reply other threads:[~2023-03-15 8:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 20:18 jspewock
2023-03-14 20:18 ` [PATCH v4 1/2] tools: expanded coverage of acvp_tool default config file jspewock
2023-03-14 20:18 ` [PATCH v4 2/2] doc: updated out-of-date acvp_tool readme jspewock
2023-03-15 8:50 ` Ali Alnubani [this message]
2023-03-15 8:52 ` [PATCH v4 0/2] tools: add acvp_tool Ali Alnubani
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=DM4PR12MB5167BCFAA93E2D39B149E42ADABF9@DM4PR12MB5167.namprd12.prod.outlook.com \
--to=alialnu@nvidia.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).