[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200711133052.GA6407@amd>
Date: Sat, 11 Jul 2020 15:30:52 +0200
From: Pavel Machek <pavel@...x.de>
To: Dan Williams <dan.j.williams@...el.com>
Cc: corbet@....net, Randy Dunlap <rdunlap@...radead.org>,
Dave Airlie <airlied@...hat.com>,
Kees Cook <keescook@...omium.org>,
SeongJae Park <sjpark@...zon.de>,
Olof Johansson <olof@...om.net>, Chris Mason <clm@...clm>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
torvalds@...ux-foundation.org,
tech-board-discuss@...ts.linuxfoundation.org,
ksummit-discuss@...ts.linuxfoundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] CodingStyle: Inclusive Terminology
On Wed 2020-07-08 00:23:59, Dan Williams wrote:
> 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.
>
> +replacements for 'blacklist/whitelist' are: 'denylist/allowlist' or
> +'blocklist/passlist'.
I don't see what is "non inclusive" about blacklist and whitelist...
Plus, please grep kernel for actual usages. blocklist/denylist is
_not_ suitable replacement for kernel use of blacklist.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Download attachment "signature.asc" of type "application/pgp-signature" (182 bytes)
Powered by blists - more mailing lists