From: Declan Doherty <declan.doherty@intel.com>
To: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] test/bonding: fix namespace bonding mode4 unit tests
Date: Wed, 5 Jul 2017 17:41:10 +0100 [thread overview]
Message-ID: <a75169ef-f865-8464-2f84-b9bcf24fbf98@intel.com> (raw)
In-Reply-To: <20170705152747.55807-1-danielx.t.mrzyglod@intel.com>
On 05/07/2017 4:27 PM, Daniel Mrzyglod wrote:
> ring network driver is limited to 32 characters
> the name of device was extened to net_ring_unit_test_mode4_slave_0 which is 33
>
> Fixes: 5e41ab250dfa ("app/test: unit tests for bonding mode 4")
>
> Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
> ---
> test/test/test_link_bonding_mode4.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/test/test/test_link_bonding_mode4.c b/test/test/test_link_bonding_mode4.c
> index c6745e8..8b64bbf 100644
> --- a/test/test/test_link_bonding_mode4.c
> +++ b/test/test/test_link_bonding_mode4.c
> @@ -73,11 +73,11 @@
> #define MAX_PKT_BURST (32)
> #define DEF_PKT_BURST (16)
>
> -#define BONDED_DEV_NAME ("unit_test_mode4_bond_dev")
> +#define BONDED_DEV_NAME ("ut_mode4_bond_dev")
>
> -#define SLAVE_DEV_NAME_FMT ("unit_test_mode4_slave_%d")
> -#define SLAVE_RX_QUEUE_FMT ("unit_test_mode4_slave_%d_rx")
> -#define SLAVE_TX_QUEUE_FMT ("unit_test_mode4_slave_%d_tx")
> +#define SLAVE_DEV_NAME_FMT ("ut_mode4_slave_%d")
> +#define SLAVE_RX_QUEUE_FMT ("ut_mode4_slave_%d_rx")
> +#define SLAVE_TX_QUEUE_FMT ("ut_mode4_slave_%d_tx")
>
> #define INVALID_SOCKET_ID (-1)
> #define INVALID_PORT_ID (0xFF)
>
Acked-by: Declan Doherty <declan.doherty@intel.com>
next prev parent reply other threads:[~2017-07-05 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 15:27 Daniel Mrzyglod
2017-07-05 16:41 ` Declan Doherty [this message]
2017-07-05 17:37 ` Ferruh Yigit
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=a75169ef-f865-8464-2f84-b9bcf24fbf98@intel.com \
--to=declan.doherty@intel.com \
--cc=danielx.t.mrzyglod@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).