[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2plzc96m4.fsf@gmail.com>
Date: Mon, 11 Dec 2023 14:05:55 +0000
From: Donald Hunter <donald.hunter@...il.com>
To: netdev@...r.kernel.org
Subject: Preferred term for netdev master / slave
I'm working on updates to the YNL spec for RTLINK and per
Documentation/process/coding-style I want to avoid any new use
of master / slave.
Recommended replacements include:
'{primary,main} / {secondary,replica,subordinate}'
'{initiator,requester} / {target,responder}'
'{controller,host} / {device,worker,proxy}'
Is there an existing preference for what to use in the context
of e.g. bridge master / slave?
If not, then how about one of:
primary / secondary
main / subordinate
Thanks!
Powered by blists - more mailing lists