From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 301EAC433DF for ; Tue, 14 Jul 2020 06:43:17 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0A248221E7 for ; Tue, 14 Jul 2020 06:43:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726061AbgGNGnQ (ORCPT ); Tue, 14 Jul 2020 02:43:16 -0400 Received: from mx2.suse.de ([195.135.220.15]:51990 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725905AbgGNGnP (ORCPT ); Tue, 14 Jul 2020 02:43:15 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id ED317B640; Tue, 14 Jul 2020 06:43:16 +0000 (UTC) Date: Tue, 14 Jul 2020 08:43:14 +0200 Message-ID: From: Takashi Iwai To: josh@joshtriplett.org Cc: Dan Williams , ksummit-discuss@lists.linuxfoundation.org, Greg Kroah-Hartman , SeongJae Park , linux-kernel@vger.kernel.org, tech-board-discuss@lists.linuxfoundation.org, James Bottomley , Dave Airlie , Christian Brauner , Dan Carpenter Subject: Re: [Ksummit-discuss] [PATCH v3] CodingStyle: Inclusive Terminology In-Reply-To: <20200714043949.GB25423@localhost> References: <159423201991.2466245.8461410729774664077.stgit@dwillia2-desk3.amr.corp.intel.com> <20200714043949.GB25423@localhost> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 14 Jul 2020 06:39:49 +0200, josh@joshtriplett.org wrote: > > On Mon, Jul 13, 2020 at 10:02:24AM +0200, Takashi Iwai wrote: > > On Wed, 08 Jul 2020 20:14:27 +0200, > > Dan Williams wrote: > > > > > > +Recommended replacements for 'blacklist/whitelist' are: > > > + 'denylist / allowlist' > > > + 'blocklist / passlist' > > > > I started looking through the tree now and noticed there are lots of > > patterns like "whitelisted" or "blacklisted". How can the words fit > > for those? Actually, there are two cases like: > > > > - Foo is blacklisted > > - Allow to load the non-whitelisted cards > > > > Currently I'm replacing the former with "Foo is in denylist", but not > > sure about the latter case. I thought Kees mentioned about this, but > > don't remember the proposal... > > I find that "blocklist" works well as a verb: "foo is blocklisted", > "blocklist foo", or in some cases just "block foo" or "deny foo". For > the second case, phrasings like "allow loading non-safelisted cards" or > "allow loading cards not on the passlist" seem clear. Yes, that makes sense. I have wished some simple replacement with sed, but it seems that it'd be better to rephrase such texts in anyway. thanks, Takashi