From: Stephen Hemminger <stephen@networkplumber.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Ahern <dsahern@kernel.org>,
Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: [PATCH iproute2] ip link: add sub-command to view and change DSA master
Date: Tue, 6 Sep 2022 14:17:19 -0700 [thread overview]
Message-ID: <20220906141719.4482f31d@hermes.local> (raw)
In-Reply-To: <05593f07-42e8-c4bd-8608-cf50e8b103d6@gmail.com>
On Tue, 6 Sep 2022 13:33:09 -0700
Florian Fainelli <f.fainelli@gmail.com> wrote:
> On 9/6/2022 1:05 PM, Andrew Lunn wrote:
> >> [ Alternative answer: how about "schnauzer"? I always liked how that word sounds. ]
> >
> > Unfortunately, it is not gender neutral, which i assume is a
> > requirement?
> >
> > Plus the plural is also schnauzer, which would make your current
> > multiple CPU/schnauzer patches confusing, unless you throw the rule
> > book out and use English pluralisation.
>
> What a nice digression, I had no idea you two mastered German that well
> :). How about "conduit" or "mgmt_port" or some variant in the same lexicon?
Is there an IEEE or PCI standard for this? What is used there?
next prev parent reply other threads:[~2022-09-06 21:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 19:00 [PATCH iproute2] ip link: add sub-command to view and change DSA master Vladimir Oltean
2022-09-06 15:29 ` Stephen Hemminger
2022-09-06 16:41 ` Vladimir Oltean
2022-09-06 16:55 ` Stephen Hemminger
2022-09-06 19:13 ` Vladimir Oltean
2022-09-06 20:05 ` Andrew Lunn
2022-09-06 20:33 ` Florian Fainelli
2022-09-06 21:17 ` Stephen Hemminger [this message]
2022-09-06 21:34 ` Florian Fainelli
2022-09-06 21:37 ` Andrew Lunn
2022-09-08 12:51 ` Vladimir Oltean
2022-09-08 14:08 ` David Ahern
2022-09-08 14:25 ` Stephen Hemminger
2022-09-08 16:11 ` Vladimir Oltean
2022-09-08 16:35 ` Florian Fainelli
2022-09-08 16:39 ` Stephen Hemminger
2022-09-09 6:09 ` Benjamin Poirier
2022-09-09 11:23 ` Vladimir Oltean
2022-09-09 15:03 ` 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=20220906141719.4482f31d@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).