netdev - Preferred term for netdev master / slave

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

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!