From: Stephen Hemminger <stephen@networkplumber.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Ahern <dsahern@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH v2 iproute2-next] ip link: add sub-command to view and change DSA master
Date: Wed, 21 Sep 2022 15:41:07 -0700 [thread overview]
Message-ID: <20220921154107.61399763@hermes.local> (raw)
In-Reply-To: <20220921183827.gkmzula73qr4afwg@skbuf>
On Wed, 21 Sep 2022 18:38:28 +0000
Vladimir Oltean <vladimir.oltean@nxp.com> wrote:
> On Wed, Sep 21, 2022 at 11:36:37AM -0700, Stephen Hemminger wrote:
> > On Wed, 21 Sep 2022 19:51:05 +0300
> > Vladimir Oltean <vladimir.oltean@nxp.com> wrote:
> >
> > > +.BI master " DEVICE"
> > > +- change the DSA master (host network interface) responsible for handling the
> > > +local traffic termination of the given DSA switch user port. The selected
> > > +interface must be eligible for operating as a DSA master of the switch tree
> > > +which the DSA user port is a part of. Eligible DSA masters are those interfaces
> > > +which have an "ethernet" reference towards their firmware node in the firmware
> > > +description of the platform, or LAG (bond, team) interfaces which contain only
> > > +such interfaces as their ports.
> >
> > We still need to find a better name for this.
> > DSA predates the LF inclusive naming but that doesn't mean it can't be
> > fixed in user visible commands.
>
> Need? Why need? Who needs this and since when?
Also see: https://www.kernel.org/doc/html/v6.0-rc6/process/coding-style.html#naming
For symbol names and documentation, avoid introducing new usage of ‘master / slave’ (or ‘slave’ independent of ‘master’) and ‘blacklist / whitelist’.
Recommended replacements for ‘master / slave’ are:
‘{primary,main} / {secondary,replica,subordinate}’ ‘{initiator,requester} / {target,responder}’ ‘{controller,host} / {device,worker,proxy}’ ‘leader / follower’ ‘director / performer’
Recommended replacements for ‘blacklist/whitelist’ are:
‘denylist / allowlist’ ‘blocklist / passlist’
Exceptions for introducing new usage is to maintain a userspace ABI/API, or when updating code for an existing (as of 2020) hardware or protocol specification that mandates those terms. For new specifications translate specification usage of the terminology to the kernel coding standard where possible.
next prev parent reply other threads:[~2022-09-21 22:41 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
2022-09-21 22:41 ` Stephen Hemminger [this message]
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=20220921154107.61399763@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew@lunn.ch \
--cc=dsahern@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.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).