Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp573233ybt; Mon, 6 Jul 2020 17:02:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx12O89cQxmmGbndqdcjAFli7oeepuFg62gd3wxk5wHj6rxkx9jwehoQovByQac9pI7R9+G X-Received: by 2002:a05:6402:3058:: with SMTP id bu24mr40740111edb.242.1594080121892; Mon, 06 Jul 2020 17:02:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594080121; cv=none; d=google.com; s=arc-20160816; b=ztbMCLDegzAvKye/wmhDrea0lWmhQGcq1OghpS8JBEzC7ZCN8osbAUC6c5bvBStd4Q h/G/wpS3O9TbdyZifkqk9tAm9YJc8a/ftlWTIQsZD8Rnq3tBh8H4yHGfgEiJPsxejevo GCl2JvG1t6wZrvK+SMSoiXQxxrfPNvdqJBjyGyViqvIu24DfOP0DX4YRv3vOgAUF9TW2 RDOqDbiJLNp7osv8pDxo+YU+KH3L1B23z5wT12Foj0Zp1OwNfnVFXCmpYvRQh0oLzCft 1g+w4B6u2h6fMp0OnlomPx25BeC9tNjKQaFJ2Jaal3KiEgtVEUFAh7uYsAQQKH4zGDSM bZfQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:references:to:subject:from:dkim-signature; bh=4nSbcQc6o8w9v6ZNEJFjfitPw+WKCLAR8ckhCop8iZ8=; b=aUDK26bQ0O97we5QyIpRVvX48KhaPV/2wNwmQV1x79+QrmNZYT+EZmiFn3cNolzoy/ oMSZ79kPPP5jH8whtPvTlobW7KOSKtIOrSqVLixPIcgBHUhNp8eHMxC7ZBtmrzUhQDDw sOEbh8afVkyXXfwGNtooa4KK5sOhKPgka62gnxlb896YSbkZi1TJb0z5/XGvudVtr+Vb wrYPhPdDMPWSDDd1kqON84avV91xNFT9SifMp7F/mKQrkYVuZOPjwtSEyGg7bULV2p01 x86I1uSnTbqwZfSrjkY7E1kLC8Pzc7BDterNbNAdN4OCVwgLCTqHnxjQZwQlkRUzRLnu z/jw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=NM57cu5h; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s6si12990863ejo.502.2020.07.06.17.01.39; Mon, 06 Jul 2020 17:02:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=NM57cu5h; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727999AbgGFX6Z (ORCPT + 99 others); Mon, 6 Jul 2020 19:58:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59344 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727046AbgGFX6Y (ORCPT ); Mon, 6 Jul 2020 19:58:24 -0400 Received: from mail-wr1-x442.google.com (mail-wr1-x442.google.com [IPv6:2a00:1450:4864:20::442]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 84744C061755 for ; Mon, 6 Jul 2020 16:58:24 -0700 (PDT) Received: by mail-wr1-x442.google.com with SMTP id f2so15215777wrp.7 for ; Mon, 06 Jul 2020 16:58:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=4nSbcQc6o8w9v6ZNEJFjfitPw+WKCLAR8ckhCop8iZ8=; b=NM57cu5hPt5WpTyLiOYNBE+EktavfXY9/G2/Ex3+2yVkNy+hJ8Jdnwp/YX/f58v7Jd s/aTm97pbiBSSSWm9d8BEYy4OiC1T+GZyAZig5GPGpO9DLnb08yCiv1JAlEz3jCHrLFy GqNDDk429tmwQDaEAqugXo1tcZGnnFoMvADCJ9HXn7H+DU/3cNkSkcY/H7mlAZpQD1is CkwxTsKZo4tJ5WBsSnfoZMATroXRXxPngNT/moD5pzoo62NzDQc73OuYV+uaRDLK1T03 izEtl6+2R183jRvTFAOQzhRPZ5bflHG/aPf08X6CgsLKCvo2kOZd7Nwr10OsbsfjEO+Z QIOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=4nSbcQc6o8w9v6ZNEJFjfitPw+WKCLAR8ckhCop8iZ8=; b=NyGR277yQrEZ0GPnC1snluMZTbIeK1WamAAS98WDnceSR/HM/8fF2AI24j4ZmCPqP/ 6SdOAOw0970YrqhSaIQENVcP1Ij/aaif1u0dwXW8RBSKTYUXIHy/OHQXM5iU7WZs3l8A eMGEIAzIHOa3V8c1I6l1/uWyue42nVGdtocIKnUNzhC0nypWGRoL/3+MXeMe8A5+TIHl LCzeYLT6iAKdxGundNe30EQfQ0xf39ctQCPaz6CmghxT6NoWvYXecpN+msJpzR0l8H66 bQXg8dhS1H3kXafx23R51gBpox7gA4UJSvJ1gws+0tnprohwxCQhApbtNbEpNOy8nJjk FhMw== X-Gm-Message-State: AOAM532Nn3Q610iIp2jqyQOLIC53BCWqjk4KhWGgRMiis8Skuv7Z9P3/ 5ktDfHBN5WEnpolpyqlVTDhH3l3E X-Received: by 2002:a5d:4dc2:: with SMTP id f2mr52188056wru.399.1594079903117; Mon, 06 Jul 2020 16:58:23 -0700 (PDT) Received: from [192.168.50.2] (178-164-237-246.pool.digikabel.hu. [178.164.237.246]) by smtp.gmail.com with ESMTPSA id l8sm25651546wrq.15.2020.07.06.16.58.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 06 Jul 2020 16:58:22 -0700 (PDT) From: Tibor Raschko Subject: Re: [Tech-board-discuss] [PATCH] CodingStyle: Inclusive Terminology To: Dan Williams , torvalds@linux-foundation.org, ksummit-discuss@lists.linuxfoundation.org, Greg Kroah-Hartman , linux-kernel@vger.kernel.org, tech-board-discuss@lists.linuxfoundation.org, Chris Mason , skhan@linuxfoundation.org References: <79214066-3886-e0ef-f26e-8cb3d53404be@linuxfoundation.org> Message-ID: Date: Tue, 7 Jul 2020 01:58:21 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <79214066-3886-e0ef-f26e-8cb3d53404be@linuxfoundation.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > The suggestions you made will help us adapt inclusive terminology > for the current times, and also help us move toward terms that are > intuitive and easier to understand keeping our global developer > community in mind. > 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. > Terms such as "whitelist" etc are contextual, hence assume contextual > knowledge on the part of the reader. We are talking about the source code of and interacting with an operating system kernel. Naturally, most things here are contextual and require domain knowledge to be understood correctly. Not requiring contextual knowledge when reading the kernel sources doesn't sound like a realistic argument. Raschko T.