From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Pavel Machek <pavel@ucw.cz>
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>,
"open list:ARM/Mediatek SoC support"
<linux-kernel@vger.kernel.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next v2 1/2] net: dsa: Use conduit and user terms
Date: Mon, 23 Oct 2023 08:50:08 -0700 [thread overview]
Message-ID: <ea6f739d-5195-41e4-a8e7-8300eebe9a86@broadcom.com> (raw)
In-Reply-To: <ZTYc6l2ZpLeGRFj9@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
Howdy,
On 10/23/2023 12:12 AM, Pavel Machek wrote:
> On Wed 2023-10-11 15:20:25, Florian Fainelli wrote:
>> Use more inclusive terms throughout the DSA subsystem by moving away
>> from "master" which is replaced by "conduit" and "slave" which is
>> replaced by "user". No functional changes.
>
> Note that by making it more "inclusive" you make it incomprehensible
> for users where english is not their first language.
We have use the term conduit and user ports a lot while discussing DSA
just never actually made that part of the code. From that angle, there
are precedent and people more or less familiar with the subsystem should
be able to retrain their muscle memory towards these concepts.
>
> Plus, "user" already means something else in kernel context, so this
> will likely be confusing even for native speakers.
I am open to other suggestions that would make it easier to grasp as a
subsystem, native speaker or else. The "user" ports are user-visible and
controllable, seems quite apt.
>
> This is wrong.
And I am afraid without more substance this is a gratuitous rejection of
change. I am not engaging into why or why we should not be doing that
effort.
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
next prev parent reply other threads:[~2023-10-23 15:50 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 [this message]
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 ` [PATCH net-next v2 0/2] Switch DSA to inclusive terminology Stephen Hemminger
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=ea6f739d-5195-41e4-a8e7-8300eebe9a86@broadcom.com \
--to=florian.fainelli@broadcom.com \
--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=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 \
--cc=pavel@ucw.cz \
/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