From: Akhil Goyal <akhil.goyal@nxp.com>
To: Ciara Power <ciara.power@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "declan.doherty@intel.com" <declan.doherty@intel.com>,
"adamx.dybkowski@intel.com" <adamx.dybkowski@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] Update crypto perf script and doc
Date: Thu, 4 Feb 2021 18:27:20 +0000 [thread overview]
Message-ID: <VI1PR04MB31681CD2D87D86A3A3A71094E6B39@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20210202165816.3767724-1-ciara.power@intel.com>
> Subject: [PATCH v2 0/3] Update crypto perf script and doc
>
> This patchset contains some fixes for the crypto perf graphing script.
>
> A release note is added, and some small fixes for the script documentation
> are also included.
> The script config handling is modified to handle EAL and app parameters
> using the same method, which fixes a bug that some formats of EAL parameters
> weren't parsed correctly.
>
> v2: Added patch for parameter handling fix.
>
Release notes should be part of the actual patch of the feature introduced.
Added reference to original patch.
Please ensure to do that in future.
Also use "app/crypto-perf: ...." as title for patches in test-crypto-perf application
Applied to dpdk-next-crypto
Thanks.
prev parent reply other threads:[~2021-02-04 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 11:48 [dpdk-dev] [PATCH 0/2] Update doc for crypto perf script Ciara Power
2021-02-02 11:48 ` [dpdk-dev] [PATCH 1/2] doc: update release notes " Ciara Power
2021-02-02 11:48 ` [dpdk-dev] [PATCH 2/2] doc: fix crypto perf script guide Ciara Power
2021-02-02 16:58 ` [dpdk-dev] [PATCH v2 0/3] Update crypto perf script and doc Ciara Power
2021-02-02 16:58 ` [dpdk-dev] [PATCH v2 1/3] doc: update release notes for crypto perf script Ciara Power
2021-02-03 10:30 ` Dybkowski, AdamX
2021-02-02 16:58 ` [dpdk-dev] [PATCH v2 2/3] doc: fix crypto perf script guide Ciara Power
2021-02-03 10:30 ` Dybkowski, AdamX
2021-02-02 16:58 ` [dpdk-dev] [PATCH v2 3/3] test/cryptodev: fix handling for config parameters Ciara Power
2021-02-03 10:31 ` Dybkowski, AdamX
2021-02-04 18:27 ` Akhil Goyal [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=VI1PR04MB31681CD2D87D86A3A3A71094E6B39@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=adamx.dybkowski@intel.com \
--cc=ciara.power@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@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).