From: Stephen Hemminger <stephen@networkplumber.org>
To: Serhey Popovych <serhe.popovych@gmail.com>
Cc: netdev@vger.kernel.org, dsahern@gmail.com
Subject: Re: [PATCH iproute2-next v2 3/7] iplink: Use "dev" and "name" parameters interchangeable when possible
Date: Tue, 20 Feb 2018 15:04:26 -0800 [thread overview]
Message-ID: <20180220150426.2d2527c5@xeon-e3> (raw)
In-Reply-To: <1519162649-22449-4-git-send-email-serhe.popovych@gmail.com>
On Tue, 20 Feb 2018 23:37:25 +0200
Serhey Popovych <serhe.popovych@gmail.com> wrote:
> Both of them accept network device name as argument, but have different
> meaning:
>
> dev - is a device by it's name,
> name - name for specific device device.
>
> The only case where they treated separately is network device rename
> case where need to specify both ifindex and new name. In rest of the
> cases we can assume that dev == name.
I would rather keep name as only being a valid argument for set command.
And reject use of:
ip li show name eth0
next prev parent reply other threads:[~2018-02-20 23:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 21:37 [PATCH iproute2-next v2 0/7] iplink: Improve iplink_parse() Serhey Popovych
2018-02-20 21:37 ` [PATCH iproute2-next v2 1/7] utils: Introduce and use nodev() helper routine Serhey Popovych
2018-02-21 5:13 ` David Ahern
2018-02-20 21:37 ` [PATCH iproute2-next v2 2/7] iplink: Correctly report error when network device isn't found Serhey Popovych
2018-02-21 5:15 ` David Ahern
2018-02-21 7:14 ` Serhey Popovych
2018-02-20 21:37 ` [PATCH iproute2-next v2 3/7] iplink: Use "dev" and "name" parameters interchangeable when possible Serhey Popovych
2018-02-20 23:04 ` Stephen Hemminger [this message]
2018-02-21 6:35 ` Serhey Popovych
2018-02-20 21:37 ` [PATCH iproute2-next v2 4/7] iplink: Follow documented behaviour when "index" is given Serhey Popovych
2018-02-20 21:37 ` [PATCH iproute2-next v2 5/7] iplink: Perform most of request buffer setups and checks in iplink_parse() Serhey Popovych
2018-02-20 21:37 ` [PATCH iproute2-next v2 6/7] iplink: Move data structures to block of their users Serhey Popovych
2018-02-20 21:37 ` [PATCH iproute2-next v2 7/7] iplink: Reduce number of arguments to iplink_parse() Serhey Popovych
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=20180220150426.2d2527c5@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=serhe.popovych@gmail.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).