Re: [PATCH v1] net/vdev_netvsc: fix creating short name devices

From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ophir Munk <ophirmu@mellanox.com>,
	dev@dpdk.org, Matan Azrad <matan@mellanox.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Olga Shern <olgas@mellanox.com>,
	stable@dpdk.org
Subject: Re: [PATCH v1] net/vdev_netvsc: fix creating short name devices
Date: Tue, 24 Apr 2018 13:56:45 +0100	[thread overview]
Message-ID: <85b96a2a-64e8-243e-86fa-7a9a9a800fec@intel.com> (raw)
In-Reply-To: <1523344821-8890-1-git-send-email-ophirmu@mellanox.com>

On 4/10/2018 8:20 AM, Ophir Munk wrote:
> Prior to this commit the vdev_netvsc PMD was creating tap and failsafe
> devices with long names, such as "net_tap_net_vdev_netvsc0" or
> "net_failsafe_net_vdev_netvsc0".
> Long names containing more than 32 characters may be rejected by some
> APIs (e.g. membuf pool creation).
> This commits fixes this issue by creating tap and failsafe devices
> with short names such as "tap_net_vsc0" or "net_failsafe_vsc0".
> 
> Fixes: e7dc5d7becc5 ("net/vdev_netvsc: implement core functionality")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Ophir Munk <ophirmu@mellanox.com>

Applied to dpdk-next-net/master, thanks.

(used suggested commit title/log [1])

[1]
net/vdev_netvsc: shorten devices names

Prior to this commit the vdev_netvsc PMD was creating tap and failsafe
devices with long names, such as "net_tap_net_vdev_netvsc0" or
"net_failsafe_net_vdev_netvsc0".
This commits creates tap and failsafe devices with short names such as
"net_tap_netvsc0" or "net_failsafe_netvsc0".