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!

Quoted 4 lines · Donald Hunter

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.

Quoted 9 lines

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?

Hi Donald,

In other projects like NetworkManager, rust-netlink libraries.. the terms that are being used in the context of linux bridging are controller / port.

Quoted 2 lines

If not, then how about one of:

Quoted 5 lines

primary / secondary
main / subordinate

Thanks!

Thanks!