From: Thomas Monjalon <thomas@monjalon.net>
To: "Trybula, ArturX" <arturx.trybula@intel.com>
Cc: dev@dpdk.org, Akhil Goyal <akhil.goyal@nxp.com>,
Shally Verma <shallyv@marvell.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"Dybkowski, AdamX" <adamx.dybkowski@intel.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH v5 1/1] app/test-compress-perf: report header improvement
Date: Fri, 19 Jul 2019 18:21:15 +0200 [thread overview]
Message-ID: <2834760.7gSptfXZDU@xps> (raw)
In-Reply-To: <VE1PR04MB663918123F3AA9708123F804E6CB0@VE1PR04MB6639.eurprd04.prod.outlook.com>
19/07/2019 15:17, Akhil Goyal:
> >
> > > +static struct cperf_buffer_info tests_res;
> > Rename test_res too --> buffer_info? You can address it in next release cycle as
> > well.
> > [Artur] Thank you Shally. Good point. Will be changed in the next cycle.
> >
> > ....
> Applied to dpdk-next-crypto
Not pulled in master tree for 2 reasons:
- the title and commit log are not descriptive enough
- there are some UTF-8 characters for no good reason in the printf.
Please stick to standard dash or asterisk for lists,
so it will be printed in any console.
next prev parent reply other threads:[~2019-07-19 16:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 10:24 [dpdk-dev] [PATCH] " Artur Trybula
2019-06-26 17:04 ` Shally Verma
2019-06-27 8:58 ` Trybula, ArturX
2019-06-27 11:00 ` Shally Verma
2019-06-27 11:46 ` Trybula, ArturX
2019-06-27 14:38 ` Shally Verma
2019-06-28 9:52 ` Trybula, ArturX
2019-07-05 6:30 ` [dpdk-dev] [PATCH v2 0/1] add extra features to test-compress-perf Artur Trybula
2019-07-05 6:30 ` [dpdk-dev] [PATCH v2 1/1] app/test-compress-perf: report header improvement Artur Trybula
2019-07-05 6:53 ` Jerin Jacob Kollanukkaran
2019-07-05 7:40 ` [dpdk-dev] [PATCH v3 0/1] add extra features to test-compress-perf Artur Trybula
2019-07-05 7:40 ` [dpdk-dev] [PATCH v3 1/1] app/test-compress-perf: report header improvement Artur Trybula
2019-07-12 10:43 ` [dpdk-dev] [PATCH v4 0/1] add extra features to test-compress-perf Artur Trybula
2019-07-12 10:43 ` [dpdk-dev] [PATCH v4 1/1] app/test-compress-perf: report header improvement Artur Trybula
2019-07-15 12:47 ` [dpdk-dev] [EXT] " Shally Verma
2019-07-15 14:01 ` Trybula, ArturX
2019-07-16 13:49 ` Trahe, Fiona
2019-07-17 7:21 ` Shally Verma
2019-07-17 11:02 ` [dpdk-dev] [PATCH v5 0/1] add extra features to test-compress-perf Artur Trybula
2019-07-17 11:02 ` [dpdk-dev] [PATCH v5 1/1] app/test-compress-perf: report header improvement Artur Trybula
2019-07-17 11:15 ` [dpdk-dev] [EXT] " Shally Verma
2019-07-17 11:26 ` Trybula, ArturX
2019-07-19 13:17 ` Akhil Goyal
2019-07-19 16:21 ` Thomas Monjalon [this message]
2019-07-19 17:37 ` Trahe, Fiona
2019-07-24 12:53 ` [dpdk-dev] [PATCH v6 0/1] add extra features to test-compress-perf Adam Dybkowski
2019-07-24 12:53 ` [dpdk-dev] [PATCH v6 1/1] app/test-compress-perf: provide more detailed report Adam Dybkowski
2019-07-24 13:55 ` [dpdk-dev] [PATCH v7 0/1] add extra features to test-compress-perf Adam Dybkowski
2019-07-24 13:55 ` [dpdk-dev] [PATCH v7 1/1] app/test-compress-perf: provide more detailed report Adam Dybkowski
2019-07-25 12:39 ` Trahe, Fiona
2019-07-26 12:41 ` Akhil Goyal
2019-07-17 11:16 ` [dpdk-dev] [EXT] [PATCH v5 0/1] add extra features to test-compress-perf Shally Verma
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=2834760.7gSptfXZDU@xps \
--to=thomas@monjalon.net \
--cc=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arturx.trybula@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=shallyv@marvell.com \
/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).