CodingStyle: Inclusive Terminology

Linux maintains a coding-style and its own idiomatic set of terminology.
Update the style guidelines to recommend replacements for the terms
master/slave and blacklist/whitelist.

Link: http://lore.kernel.org/r/159389297140.2210796.13590142254668787525.stgit@dwillia2-desk3.amr.corp.intel.com
Acked-by: Randy Dunlap <[email protected]>
Acked-by: Dave Airlie <[email protected]>
Acked-by: SeongJae Park <[email protected]>
Acked-by: Christian Brauner <[email protected]>
Acked-by: James Bottomley <[email protected]>
Acked-by: Daniel Vetter <[email protected]>
Acked-by: Andy Lutomirski <[email protected]>
Acked-by: Laura Abbott <[email protected]>
Acked-by: Gustavo A. R. Silva <[email protected]>
Reviewed-by: Matthias Brugger <[email protected]>
Reviewed-by: Mark Brown <[email protected]>
Signed-off-by: Stephen Hemminger <[email protected]>
Signed-off-by: Theodore Ts'o <[email protected]>
Signed-off-by: Shuah Khan <[email protected]>
Signed-off-by: Dan Carpenter <[email protected]>
Signed-off-by: Kees Cook <[email protected]>
Signed-off-by: Olof Johansson <[email protected]>
Signed-off-by: Jonathan Corbet <[email protected]>
Signed-off-by: Chris Mason <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Signed-off-by: Dan Williams <[email protected]>

Author: djbw

Documentation/process/coding-style.rst

@@ -319,6 +319,26 @@ If you are afraid to mix up your local variable names, you have another
 problem, which is called the function-growth-hormone-imbalance syndrome.
 See chapter 6 (Functions).
 
+For symbol names and documentation, avoid introducing new usage of
+'master / slave' (or 'slave' independent of 'master') and 'blacklist /
+whitelist'.
+
+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 a userspace ABI/API,
+or when updating code for an existing (as of 2020) hardware or protocol
+specification that mandates those terms. For new specifications
+translate specification usage of the terminology to the kernel coding
+standard where possible.
 
 5) Typedefs
 -----------