From: Declan Doherty <declan.doherty@intel.com>
To: Tomasz Kulasek <tomaszx.kulasek@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] test: fix bonded device name
Date: Wed, 26 Jul 2017 18:06:46 +0100 [thread overview]
Message-ID: <11d2cd9c-f7de-5cae-37fe-67434334d696@intel.com> (raw)
In-Reply-To: <20170726154829.32736-1-tomaszx.kulasek@intel.com>
On 26/07/2017 4:48 PM, Tomasz Kulasek wrote:
> Bonding devices name must start with "net_bonding" prefix.
>
> Fixes: 9bf4901d1a11 ("bus/vdev: remove probe with driver name option")
>
> Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>
> ---
> test/test/test_link_bonding.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/test/test/test_link_bonding.c b/test/test/test_link_bonding.c
> index aa2a1a2..828f7f7 100644
> --- a/test/test/test_link_bonding.c
> +++ b/test/test/test_link_bonding.c
> @@ -83,7 +83,7 @@
> #define MAX_PKT_BURST (512)
> #define DEF_PKT_BURST (16)
>
> -#define BONDED_DEV_NAME ("unit_test_bond_dev")
> +#define BONDED_DEV_NAME ("net_bonding_ut")
>
> #define INVALID_SOCKET_ID (-1)
> #define INVALID_PORT_ID (-1)
> @@ -939,7 +939,7 @@ struct rte_fdir_conf fdir_conf = {
> /*
> * 1. a - Create / configure bonded / slave ethdevs
> */
> - bonded_port_id = rte_eth_bond_create("ethdev_bond_mac_ass_test",
> + bonded_port_id = rte_eth_bond_create("net_bonding_mac_ass_test",
> BONDING_MODE_ACTIVE_BACKUP, rte_socket_id());
> TEST_ASSERT(bonded_port_id > 0, "failed to create bonded device");
>
>
Acked-by: Declan Doherty <declan.doherty@intel.com>
next prev parent reply other threads:[~2017-07-26 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 15:48 Tomasz Kulasek
2017-07-26 17:06 ` Declan Doherty [this message]
2017-07-31 15:53 ` 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=11d2cd9c-f7de-5cae-37fe-67434334d696@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).