[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220922193648.5pt4w7vt4ucw3ubb@skbuf>
Date: Thu, 22 Sep 2022 19:36:49 +0000
From: Vladimir Oltean <vladimir.oltean@....com>
To: Stephen Hemminger <stephen@...workplumber.org>
CC: Andrew Lunn <andrew@...n.ch>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
David Ahern <dsahern@...nel.org>,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>
Subject: Re: [PATCH v2 iproute2-next] ip link: add sub-command to view and
change DSA master
On Thu, Sep 22, 2022 at 12:04:49PM -0700, Stephen Hemminger wrote:
> My preference would be that a non-offensive term was used and put
> as the preferred choice in the man page. The other terms like master
> will be accepted as synonyms.
Ok, if there aren't any objections, I will propose a v3 in 30 minutes or
so, with 'conduit' being the primary iproute2 keyword and 'master'
defined in the man page as a synonym for it, and the ip-link program
printing just 'conduit' in the help text but parsing both, and printing
just 'conduit' in the json output. At least this term has some history
of being used in Documentation/networking/dsa/dsa.rst, although not
unambiguously so. There is one paragraph in there which also mentions
DSA (cascade) ports as conduits. Though I really don't have any better
idea.
Powered by blists - more mailing lists