From: Thomas Monjalon <thomas@monjalon.net>
To: Naga Suresh Somarowthu <naga.sureshx.somarowthu@intel.com>
Cc: dev@dpdk.org, reshma.pattan@intel.com, anatoly.burakov@intel.com,
remy.horton@intel.com
Subject: Re: [dpdk-dev] [PATCH v14 0/4] add unit tests for bitrate, latency and pdump libraries
Date: Fri, 18 Jan 2019 02:34:46 +0100 [thread overview]
Message-ID: <25805038.YpNabzTz1s@xps> (raw)
In-Reply-To: <1539000767-22745-1-git-send-email-naga.sureshx.somarowthu@intel.com>
08/10/2018 14:12, Naga Suresh Somarowthu:
> 1/4: add helper functions for tests using ring-PMD Rx/Tx
> 2/4: unit test cases added for bitrate library
> 3/4: unit test cases added for latencystats library
> 4/4: unit test cases added for pdump library
>
> Patches 2/4, 3/4 and 4/4 depends on 1/4
>
> Signed-off-by: Naga Suresh Somarowthu <naga.sureshx.somarowthu@intel.com>
> Reviewed-by: Reshma Pattan <reshma.pattan@intel.com>
> Acked-by: Reshma Pattan <reshma.pattan@intel.com>
>
> ---
> v14 :rebased
> v13: added required changes for meson build
> updated respective patches
> updated the headers as per IWYU
> v12: corrected commit message for pdump unit test
> v11: fixed compilation issue in centos and 32bit arch
> removed memzone free as per fix in the latency library
> and updated the maintainers file
> v10: fixed clang compiler issues and freed latency stats memzone in latency stats unit tests.
> v9: rebased ontop of latest autotest changes and added new tests to the autotest list
> v8: renamed commit headline and freed the metrics memzone for bitrate ut
> v7: removed unused macros and corrected the comment
> v6: updated ring variable appropriately
> v5: rebased, freed pools and rings, created common patch set
> ---
>
> Naga Suresh Somarowthu (4):
> test: add helper functions for tests using ring-PMD Rx/Tx
> test: add unit tests for bitrate library
> test: add unit tests for latencystats library
> test: add unit test for pdump library
Rebased and applied, thanks
next prev parent reply other threads:[~2019-01-18 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1535115087-2442-1>
2018-10-08 12:12 ` Naga Suresh Somarowthu
2019-01-18 1:34 ` Thomas Monjalon [this message]
2018-10-08 12:12 ` [dpdk-dev] [PATCH v14 1/4] test: add helper functions for tests using ring-PMD Rx/Tx Naga Suresh Somarowthu
2018-10-08 12:12 ` [dpdk-dev] [PATCH v14 2/4] test: add unit tests for bitrate library Naga Suresh Somarowthu
2018-10-08 12:12 ` [dpdk-dev] [PATCH v14 3/4] test: add unit tests for latencystats library Naga Suresh Somarowthu
2018-10-08 12:12 ` [dpdk-dev] [PATCH v14 4/4] test: add unit test for pdump library Naga Suresh Somarowthu
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=25805038.YpNabzTz1s@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=naga.sureshx.somarowthu@intel.com \
--cc=remy.horton@intel.com \
--cc=reshma.pattan@intel.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).