Messages in this thread |  | | Subject | Re: [Ksummit-discuss] [Tech-board-discuss] [PATCH] CodingStyle: Inclusive Terminology | From | Shuah Khan <> | Date | Thu, 9 Jul 2020 10:01:18 -0600 |
| |
On 7/9/20 4:43 AM, Mauro Carvalho Chehab wrote: > Em Tue, 7 Jul 2020 01:58:21 +0200 > Tibor Raschko <tibrasch@gmail.com> escreveu: > >>> Allowlist/denylist terms are intuitive and action based which have a >>> globally uniform meaning. >> >> Nobody has a problem understanding "blacklist" and "whitelist". These >> are universally understood words even outside of computing. Claiming >> that we need clearer alternatives is smoke and mirrors. > > Actually, as a non-native English speaker, the first time I saw > "<color>list", I had to do some research in order to understand what it > means :-)
Thanks for the perspective. This is why we need clear and uniform words. Our community is global. English isn't English everywhere either.
> > That reminds me: what about "graylist"? > > For coherency, if "blacklist/whitelist" won't be used anymore, an > alternative to graylist should also be provided. > > Right now, it seems that only ACPI uses it: > > $ git grep -i graylist > drivers/clocksource/acpi_pm.c:static void acpi_pm_check_graylist(struct pci_dev *dev) > drivers/clocksource/acpi_pm.c: acpi_pm_check_graylist); > drivers/clocksource/acpi_pm.c: acpi_pm_check_graylist); >
What is "graylist"? Does it mean in between allow/deny?
thanks, -- Shuah
|  |