[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200709161351.GF4960@sirena.org.uk>
Date: Thu, 9 Jul 2020 17:13:51 +0100
From: Mark Brown <broonie@...nel.org>
To: Shuah Khan <skhan@...uxfoundation.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
Tibor Raschko <tibrasch@...il.com>,
ksummit-discuss@...ts.linuxfoundation.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org,
tech-board-discuss@...ts.linuxfoundation.org,
Chris Mason <clm@...clm>, torvalds@...ux-foundation.org
Subject: Re: [Tech-board-discuss] [Ksummit-discuss] [PATCH] CodingStyle:
Inclusive Terminology
On Thu, Jul 09, 2020 at 10:01:18AM -0600, Shuah Khan wrote:
> On 7/9/20 4:43 AM, Mauro Carvalho Chehab wrote:
> > For coherency, if "blacklist/whitelist" won't be used anymore, an
> > alternative to graylist should also be provided.
> What is "graylist"? Does it mean in between allow/deny?
Yes. Typically it's used in situations where you don't want to deny
something but might for example want to do extra checks to verify that
things are OK.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists