[PATCH] coding-style: Adds examples for alternatives to 'blacklist'

[PATCH] coding-style: Adds examples for alternatives to 'blacklist'

[Paul Schulz]

Replacing the term 'blacklist' with a term that better describes
a lists functionality or it's use makes its usage more understandable,
rather than a generic 'denylist' or 'blocklist'

eg. 'quirklist' for hardware cards what behave differently
    'invalidlist' for a list of invalid hardware strings

Signed-off-by: Paul Schulz <paul@mawsonlakes.org>
---
 Documentation/process/coding-style.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/process/coding-style.rst b/Documentation/process/coding-style.rst
index 1bee6f8affdb..3e5ca93a4443 100644
--- a/Documentation/process/coding-style.rst
+++ b/Documentation/process/coding-style.rst
@@ -334,6 +334,10 @@ Recommended replacements for 'blacklist/whitelist' are:
     'denylist / allowlist'
     'blocklist / passlist'
 
+Specific reasons for a lists functionality should also be considered. eg
+    'quirklist'
+    'invalidlist'
+
 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
-- 
2.25.1