From: David Ahern <dsahern@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>, netdev@vger.kernel.org
Cc: davem@davemloft.net, jakub.kicinski@netronome.com,
stephen@networkplumber.org, roopa@cumulusnetworks.com,
dcbw@redhat.com, nikolay@cumulusnetworks.com, mkubecek@suse.cz,
andrew@lunn.ch, parav@mellanox.com, saeedm@mellanox.com,
f.fainelli@gmail.com, sd@queasysnail.net, sbrivio@redhat.com,
pabeni@redhat.com, mlxsw@mellanox.com
Subject: Re: [patch iproute2-next v5 0/3] ip: add support for alternative names
Date: Sun, 27 Oct 2019 11:16:25 -0600 [thread overview]
Message-ID: <c8201b72-90c4-d8e6-65b9-b7f7ed55f0f5@gmail.com> (raw)
In-Reply-To: <20191024102052.4118-1-jiri@resnulli.us>
On 10/24/19 4:20 AM, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@mellanox.com>
>
> This patchset adds support for alternative names caching,
> manipulation and usage.
>
something is still not right with this change:
$ ip li add veth1 type veth peer name veth2
$ ip li prop add dev veth1 altname veth1_by_another_name
$ ip li sh dev veth1
15: veth1@veth2: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state
DOWN mode DEFAULT group default qlen 1000
link/ether 1e:6e:bc:26:52:f6 brd ff:ff:ff:ff:ff:ff
altname veth1_by_another_name
$ ip li sh dev veth1_by_another_name
Device "veth1_by_another_name" does not exist.
$ ip li set dev veth1_by_another_name up
Error: argument "veth1_by_another_name" is wrong: "dev" not a valid ifname
next prev parent reply other threads:[~2019-10-27 17:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 10:20 [patch iproute2-next v5 0/3] ip: add support for alternative names Jiri Pirko
2019-10-24 10:20 ` [patch iproute2-next v5 1/3] lib/ll_map: cache " Jiri Pirko
2019-10-24 10:20 ` [patch iproute2-next v5 2/3] ip: add support for alternative name addition/deletion/list Jiri Pirko
2019-10-24 10:20 ` [patch iproute2-next v5 3/3] ip: allow to use alternative names as handle Jiri Pirko
2019-10-27 17:16 ` David Ahern [this message]
2019-10-28 7:38 ` [patch iproute2-next v5 0/3] ip: add support for alternative names Jiri Pirko
2019-10-28 14:49 ` David Ahern
2019-10-28 18:19 ` Jiri Pirko
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=c8201b72-90c4-d8e6-65b9-b7f7ed55f0f5@gmail.com \
--to=dsahern@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=f.fainelli@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@resnulli.us \
--cc=mkubecek@suse.cz \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=pabeni@redhat.com \
--cc=parav@mellanox.com \
--cc=roopa@cumulusnetworks.com \
--cc=saeedm@mellanox.com \
--cc=sbrivio@redhat.com \
--cc=sd@queasysnail.net \
--cc=stephen@networkplumber.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).