ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: josh@joshtriplett.org
Cc: ksummit-discuss@lists.linuxfoundation.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	SeongJae Park <sjpark@amazon.de>,
	linux-kernel@vger.kernel.org,
	tech-board-discuss@lists.linuxfoundation.org,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Dave Airlie <airlied@redhat.com>,
	Christian Brauner <christian.brauner@ubuntu.com>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Ksummit-discuss] [PATCH v3] CodingStyle: Inclusive Terminology
Date: Tue, 14 Jul 2020 08:43:14 +0200	[thread overview]
Message-ID: <s5ha702wq9p.wl-tiwai@suse.de> (raw)
In-Reply-To: <20200714043949.GB25423@localhost>

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

_______________________________________________
Ksummit-discuss mailing list
Ksummit-discuss@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss

  reply	other threads:[~2020-07-14  6:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-08 18:14 Dan Williams
2020-07-09  7:25 ` Daniel Vetter
2020-07-09 19:08   ` Dan Williams
2020-07-09  9:45 ` Matthias Brugger
2020-07-09 19:10   ` Dan Williams
2020-07-10 21:12 ` Andy Lutomirski
2020-07-10 21:46   ` Dan Williams
2020-07-10 21:13 ` Laura Abbott
2020-07-10 21:48   ` Dan Williams
2020-07-11 20:31 ` josh
2020-07-13  4:20 ` Vinod Koul
2020-07-13  7:49 ` Joerg Roedel
2020-07-13  8:02 ` Takashi Iwai
2020-07-13  8:43   ` Julia Lawall
2020-07-13  9:36     ` Takashi Iwai
2020-07-13  9:39       ` Julia Lawall
2020-07-13  9:44         ` Takashi Iwai
2020-07-13 15:06   ` [Ksummit-discuss] [Tech-board-discuss] " James Bottomley
2020-07-14  4:39   ` [Ksummit-discuss] " josh
2020-07-14  6:43     ` Takashi Iwai [this message]
2020-07-17 16:47   ` Andy Lutomirski
2020-07-15 12:19 ` Jani Nikula
2020-07-17  8:36 ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5ha702wq9p.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=airlied@redhat.com \
    --cc=christian.brauner@ubuntu.com \
    --cc=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=josh@joshtriplett.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sjpark@amazon.de \
    --cc=tech-board-discuss@lists.linuxfoundation.org \
    --subject='Re: [Ksummit-discuss] [PATCH v3] CodingStyle: Inclusive Terminology' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).