From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Ahern <dsahern@kernel.org>,
Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: [PATCH v2 iproute2-next] ip link: add sub-command to view and change DSA master
Date: Thu, 22 Sep 2022 21:52:52 +0000 [thread overview]
Message-ID: <20220922215251.edmytm4u6uahrd3m@skbuf> (raw)
In-Reply-To: <YyzWkuFL+gPubz2M@lunn.ch>
On Thu, Sep 22, 2022 at 11:41:38PM +0200, Andrew Lunn wrote:
> 'via' would be totally new, and i don't see any need to introduce a
> new term.
Well, the entire command is new, so...
Jakub clarified that 'via' would indeed be used as a preposition rather
than as a noun. So it does not describe eth0, but just the relationship
between swp0 and eth0 (specifically their traffic), and therefore it
isn't really a new, or alternative, naming convention for a DSA master
(which 'conduit' is, on the other hand).
What I find a bit awkward is the 'set ... type dsa via ..." syntax,
since a noun would typically be expected in place of 'via'.
next prev parent reply other threads:[~2022-09-22 21:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 16:51 [PATCH v2 iproute2-next] ip link: add sub-command to view and change DSA master Vladimir Oltean
2022-09-21 18:36 ` Stephen Hemminger
2022-09-21 18:38 ` Vladimir Oltean
2022-09-21 22:33 ` Stephen Hemminger
2022-09-22 14:41 ` Vladimir Oltean
2022-09-22 15:30 ` Stephen Hemminger
2022-09-22 15:42 ` Andrew Lunn
2022-09-22 18:43 ` Vladimir Oltean
2022-09-22 19:04 ` Stephen Hemminger
2022-09-22 19:36 ` Vladimir Oltean
2022-09-22 20:34 ` Andrew Lunn
2022-09-22 21:25 ` Florian Fainelli
2022-09-22 21:28 ` Vladimir Oltean
2022-09-22 21:30 ` Florian Fainelli
2022-09-22 21:40 ` Vladimir Oltean
2022-09-22 21:41 ` Andrew Lunn
2022-09-22 21:52 ` Vladimir Oltean [this message]
2022-09-21 22:41 ` Stephen Hemminger
2022-09-22 1:30 ` Andrew Lunn
2022-09-22 13:24 ` Jakub Kicinski
2022-09-22 15:27 ` Stephen Hemminger
2022-09-22 15:36 ` Florian Fainelli
2022-09-22 18:00 ` Vladimir Oltean
2022-09-22 19:30 ` Jakub Kicinski
2022-09-22 20:13 ` Vladimir Oltean
2022-09-22 20:28 ` Stephen Hemminger
2022-09-22 20:36 ` Vladimir Oltean
2022-09-22 21:28 ` Florian Fainelli
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=20220922215251.edmytm4u6uahrd3m@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=dsahern@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vivien.didelot@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