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: [dpdk-stable] [dpdk-dev] [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".
prev parent reply other threads:[~2018-04-24 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 7:20 [dpdk-stable] " Ophir Munk
2018-04-10 8:04 ` Matan Azrad
2018-04-10 15:35 ` Ophir Munk
2018-04-10 15:39 ` Matan Azrad
2018-04-24 14:19 ` Ferruh Yigit
2018-04-25 10:25 ` Matan Azrad
2018-04-25 10:29 ` Ferruh Yigit
2018-04-25 10:33 ` Matan Azrad
2018-04-25 10:49 ` [dpdk-stable] [dpdk-dev] " Ferruh Yigit
2018-04-24 12:56 ` Ferruh Yigit [this message]
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=85b96a2a-64e8-243e-86fa-7a9a9a800fec@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).