From: Declan Doherty <declan.doherty@intel.com>
To: Tomasz Kulasek <tomaszx.kulasek@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4 0/4] Unit tests for mode 4
Date: Fri, 13 Feb 2015 11:08:00 +0000 [thread overview]
Message-ID: <54DDDB10.2070307@intel.com> (raw)
In-Reply-To: <1423823896-4620-1-git-send-email-tomaszx.kulasek@intel.com>
On 13/02/15 10:38, Tomasz Kulasek wrote:
> This patch series depends of "PMD ring" patches and should be applied after them
> to run successfully.
>
> v4 changes
> - Adapting to changes in the initialize_eth_header API
> - Fix linking problem against librte_pmd_bond.so for shared libraries
> - Patchset cleanup for smoother application
>
> v3 changes
> - Fix compilation issues for dynamic libraries
> - Re-create a series of patches to maintain consistency
>
> v2 changes
> - Patch split for better readability
>
> Tomasz Kulasek (4):
> test: test.h rework
> test: Unit tests for mode 4
> mk: Link test app against librte_pmd_ring when needed
> pmd_bond: Set routines required by test app global
>
> app/test/Makefile | 16 +
> app/test/test.h | 112 +-
> app/test/test_link_bonding.c | 2 +-
> app/test/test_link_bonding_mode4.c | 1413 ++++++++++++++++++++++++++
> lib/librte_pmd_bond/rte_eth_bond_version.map | 2 +
> 5 files changed, 1498 insertions(+), 47 deletions(-)
> create mode 100644 app/test/test_link_bonding_mode4.c
>
Series Acked-by: Declan Doherty <declan.doherty@intel.com>
next prev parent reply other threads:[~2015-02-13 11:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 9:14 [dpdk-dev] [PATCH 0/3] bond mode 4: add unit tests Michal Jastrzebski
2014-12-12 9:14 ` [dpdk-dev] [PATCH 1/3] bond change warning Michal Jastrzebski
2015-02-18 18:06 ` Thomas Monjalon
2014-12-12 9:14 ` [dpdk-dev] [PATCH 2/3] PMD ring MAC management, fix initialization, link up/down Michal Jastrzebski
2015-01-15 10:53 ` Thomas Monjalon
2015-01-19 11:56 ` [dpdk-dev] [PATCH v2 0/3] " Tomasz Kulasek
2015-01-19 11:56 ` [dpdk-dev] [PATCH v2 1/3] PMD Ring - Add link up/down functions Tomasz Kulasek
2015-01-19 11:56 ` [dpdk-dev] [PATCH v2 2/3] PMD Ring - Add MAC addr add/remove functions Tomasz Kulasek
2015-01-19 11:56 ` [dpdk-dev] [PATCH v2 3/3] PMD Ring - Fix for MAC per device management Tomasz Kulasek
2015-01-28 11:56 ` [dpdk-dev] [PATCH v2 0/3] PMD ring MAC management, fix initialization, link up/down Doherty, Declan
2015-02-18 17:33 ` Thomas Monjalon
2014-12-12 9:14 ` [dpdk-dev] [PATCH 3/3] unit tests add mode 4 unit test Michal Jastrzebski
2015-01-15 10:55 ` Thomas Monjalon
2015-01-19 12:43 ` [dpdk-dev] [PATCH v2 0/2] " Tomasz Kulasek
2015-01-19 12:43 ` [dpdk-dev] [PATCH v2 1/2] Unit tests - test.h rework Tomasz Kulasek
2015-01-19 12:43 ` [dpdk-dev] [PATCH v2 2/2] Unit tests for mode 4 Tomasz Kulasek
2015-01-29 8:51 ` [dpdk-dev] [PATCH v3 0/3] " Tomasz Kulasek
2015-01-29 8:51 ` [dpdk-dev] [PATCH v3 1/3] test: test.h rework Tomasz Kulasek
2015-01-29 8:51 ` [dpdk-dev] [PATCH v3 2/3] test: Unit tests for mode 4 Tomasz Kulasek
2015-02-12 11:49 ` Declan Doherty
2015-01-29 8:51 ` [dpdk-dev] [PATCH v3] mk: Link test app against librte_pmd_ring when needed Tomasz Kulasek
2015-02-12 11:50 ` Declan Doherty
2015-02-13 10:38 ` [dpdk-dev] [PATCH v4 0/4] Unit tests for mode 4 Tomasz Kulasek
2015-02-13 10:38 ` [dpdk-dev] [PATCH v4 1/4] test: test.h rework Tomasz Kulasek
2015-02-13 10:38 ` [dpdk-dev] [PATCH v4 2/4] test: Unit tests for mode 4 Tomasz Kulasek
2015-02-13 10:38 ` [dpdk-dev] [PATCH v4 3/4] mk: Link test app against librte_pmd_ring when needed Tomasz Kulasek
2015-02-13 10:38 ` [dpdk-dev] [PATCH v4 4/4] pmd_bond: Set routines required by test app global Tomasz Kulasek
2015-02-13 11:08 ` Declan Doherty [this message]
2015-02-18 18:00 ` [dpdk-dev] [PATCH v4 0/4] Unit tests for mode 4 Thomas Monjalon
2014-12-12 15:27 ` [dpdk-dev] [PATCH 0/3] bond mode 4: add unit tests Doherty, Declan
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=54DDDB10.2070307@intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=tomaszx.kulasek@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).