From: Stephen Hemminger <stephen@networkplumber.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
linux-kernel@vger.kernel.org (open list:ARM/Mediatek SoC support),
linux-arm-kernel@lists.infradead.org (moderated
list:ARM/Mediatek SoC support)
Subject: Re: [PATCH net-next v2 0/2] Switch DSA to inclusive terminology
Date: Wed, 11 Oct 2023 16:22:55 -0700 [thread overview]
Message-ID: <20231011162255.6c00bd6d@hermes.local> (raw)
In-Reply-To: <20231011222026.4181654-1-florian.fainelli@broadcom.com>
On Wed, 11 Oct 2023 15:20:24 -0700
Florian Fainelli <florian.fainelli@broadcom.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.
prev parent reply other threads:[~2023-10-11 23:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 22:20 [PATCH net-next v2 0/2] Switch DSA to inclusive terminology Florian Fainelli
2023-10-11 22:20 ` [PATCH net-next v2 1/2] net: dsa: Use conduit and user terms Florian Fainelli
2023-10-12 21:23 ` Andrew Lunn
2023-10-12 23:10 ` Vladimir Oltean
2023-10-13 2:27 ` Stephen Hemminger
2023-10-13 16:25 ` Stephen Hemminger
2023-10-13 16:27 ` Florian Fainelli
2023-10-23 7:12 ` Pavel Machek
2023-10-23 15:50 ` Florian Fainelli
2023-10-23 19:32 ` Vladimir Oltean
2023-10-11 22:20 ` [PATCH net-next v2 2/2] net: dsa: Rename IFLA_DSA_MASTER to IFLA_DSA_CONDUIT Florian Fainelli
2023-10-11 23:30 ` Stephen Hemminger
2023-10-12 23:13 ` Vladimir Oltean
2023-10-13 2:30 ` Stephen Hemminger
2023-10-11 23:22 ` Stephen Hemminger [this message]
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=20231011162255.6c00bd6d@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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).