diff mbox series

[v6,01/18] doc/coding_style: add policy about master/slave

Message ID 20201014152756.6518-2-stephen@networkplumber.org (mailing list archive)
State Superseded, archived
Delegated to: Thomas Monjalon
Headers show
Series Replace terms master/slave | expand


Context Check Description
ci/checkpatch warning coding style issues

Commit Message

Stephen Hemminger Oct. 14, 2020, 3:27 p.m. UTC
Update the coding style document to include a policy against
introducing new master/slave usage. This is taken from the similar
place in the Linux kernel coding style.

Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
 doc/guides/contributing/coding_style.rst | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)
diff mbox series


diff --git a/doc/guides/contributing/coding_style.rst b/doc/guides/contributing/coding_style.rst
index d19b646fc6d7..5b4b71e2a416 100644
--- a/doc/guides/contributing/coding_style.rst
+++ b/doc/guides/contributing/coding_style.rst
@@ -283,6 +283,29 @@  Thus, the previous example would be better written:
 DPDK also provides an optimized way to store elements in lockless rings.
 This should be used in all data-path code, when there are several consumer and/or producers to avoid locking for concurrent access.
+For symbol names and documentation, new usage of
+'master / slave' (or 'slave' independent of 'master') and 'blacklist /
+whitelist' is not allowed.
+Recommended replacements for 'master / slave' are:
+    '{primary,main} / {secondary,replica,subordinate}'
+    '{initiator,requester} / {target,responder}'
+    '{controller,host} / {device,worker,proxy}'
+    'leader / follower'
+    'director / performer'
+Recommended replacements for 'blacklist/whitelist' are:
+    'denylist / allowlist'
+    'blocklist / passlist'
+Exceptions for introducing new usage is to maintain compatability
+with an existing (as of 2020) hardware or protocol
+specification that mandates those terms.