From 3444b029324bb2bd54a6bbd486792d49619e9383 Mon Sep 17 00:00:00 2001 From: Aleksander Morgado Date: Thu, 4 Nov 2021 22:40:28 +0100 Subject: core: replace 'whitelist' with 'allowlist' and 'blacklist' with 'blocklist' We keep the 'WHITELIST-ONLY' filter type name still as an option in --filter-policy=[POLICY], but deprecated and with the better 'ALLOWLIST-ONLY' replacement suggested from now on. --- include/ModemManager-tags.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'include') diff --git a/include/ModemManager-tags.h b/include/ModemManager-tags.h index decb4527..8eb8324f 100644 --- a/include/ModemManager-tags.h +++ b/include/ModemManager-tags.h @@ -68,8 +68,8 @@ * * This is a device-specific tag that allows explicitly requesting the * processing of all ports exposed by the device. This tag is usually - * used by users when the daemon runs with WHITELIST-ONLY filter policy - * type, and is associated to the MM_FILTER_RULE_EXPLICIT_WHITELIST rule. + * used by users when the daemon runs with ALLOWLIST-ONLY filter policy + * type, and is associated to the MM_FILTER_RULE_EXPLICIT_ALLOWLIST rule. * * This tag may also be specified in specific ports, e.g. when the modem * exposes a single platform port without any parent device. @@ -87,7 +87,7 @@ * This tag was originally applicable to TTY ports and only when running * in certain filter policy types. Since 1.12, this tag applies to all * filter types and to all port types (not only TTYs), and is associated - * to the MM_FILTER_RULE_EXPLICIT_BLACKLIST rule. + * to the MM_FILTER_RULE_EXPLICIT_BLOCKLIST rule. * * Since: 1.10 */ -- cgit v1.2.3-70-g09d2