[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231011162255.6c00bd6d@hermes.local>
Date: Wed, 11 Oct 2023 16:22:55 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Florian Fainelli <florian.fainelli@...adcom.com>
Cc: netdev@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@...adcom.com>,
linux-kernel@...r.kernel.org (open list:ARM/Mediatek SoC support),
linux-arm-kernel@...ts.infradead.org (moderated list:ARM/Mediatek SoC
support)
Subject: Re: [PATCH net-next v2 0/2] Switch DSA to inclusive terminology
On Wed, 11 Oct 2023 15:20:24 -0700
Florian Fainelli <florian.fainelli@...adcom.com> wrote:
> One of the action items following Netconf'23 is to switch subsystems to
> use inclusive terminology. DSA has been making extensive use of the
> "master" and "slave" words which are now replaced by "conduit" and
> "user" respectively.
Good to see this.
I started on doing this in iproute2 CLI terms for bridge and bonding,
still a work in progress.
Powered by blists - more mailing lists