qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	qemu-block@nongnu.org, qemu-trivial@nongnu.org,
	"Michael Roth" <michael.roth@amd.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	"Max Reitz" <mreitz@redhat.com>,
	"Eduardo Otubo" <otubo@redhat.com>,
	"Alex Williamson" <alex.williamson@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Aurelien Jarno" <aurelien@aurel32.net>
Subject: [PATCH v3 0/5] misc: Replace the words 'blacklist/whitelist'
Date: Wed,  3 Mar 2021 19:46:39 +0100	[thread overview]
Message-ID: <20210303184644.1639691-1-philmd@redhat.com> (raw)

Follow the inclusive terminology from the "Conscious Language in your
Open Source Projects" guidelines [*] and replace the words "blacklist"
and "whitelist" appropriately.

Since v2:
- added R-b tags
- reworded seccomp comment (thuth)
- dropped queued vfio patch
- dropped device-crash-test reworked by Eduardo as commit 1a14d4e16af
  ("device-crash-test: Remove problematic language")

Since v1:
- dropped qemu-guest-agent patches
- addressed review comments
- added R-b tags

Series fully reviewed and expected to go via the qemu-trivial@ tree.

[*] https://github.com/conscious-lang/conscious-lang-docs/blob/main/faq.md

Philippe Mathieu-Daudé (5):
  ui: Replace the word 'whitelist'
  scripts/tracetool: Replace the word 'whitelist'
  seccomp: Replace the word 'blacklist'
  qemu-options: Replace the word 'blacklist'
  tests/fp/fp-test: Replace the word 'blacklist'

 softmmu/qemu-seccomp.c        | 16 ++++++++--------
 tests/fp/fp-test.c            |  8 ++++----
 ui/console.c                  |  2 +-
 ui/vnc-auth-sasl.c            |  4 ++--
 qemu-options.hx               |  6 +++---
 scripts/tracetool/__init__.py |  2 +-
 6 files changed, 19 insertions(+), 19 deletions(-)

-- 
2.26.2




             reply	other threads:[~2021-03-03 18:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-03 18:46 Philippe Mathieu-Daudé [this message]
2021-03-03 18:46 ` [PATCH v3 1/5] ui: Replace the word 'whitelist' Philippe Mathieu-Daudé
2021-03-09 21:13   ` Laurent Vivier
2021-03-03 18:46 ` [PATCH v3 2/5] scripts/tracetool: " Philippe Mathieu-Daudé
2021-03-08 16:17   ` Stefan Hajnoczi
2021-03-09 21:14   ` Laurent Vivier
2021-03-03 18:46 ` [PATCH v3 3/5] seccomp: Replace the word 'blacklist' Philippe Mathieu-Daudé
2021-03-04  5:33   ` Thomas Huth
2021-03-09 21:15   ` Laurent Vivier
2021-03-03 18:46 ` [PATCH v3 4/5] qemu-options: " Philippe Mathieu-Daudé
2021-03-04  5:36   ` Thomas Huth
2021-03-03 18:46 ` [PATCH v3 5/5] tests/fp/fp-test: " Philippe Mathieu-Daudé
2021-03-04  5:38   ` Thomas Huth
2021-03-09 21:17   ` Laurent Vivier

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=20210303184644.1639691-1-philmd@redhat.com \
    --to=philmd@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=alex.williamson@redhat.com \
    --cc=aurelien@aurel32.net \
    --cc=dgilbert@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=mreitz@redhat.com \
    --cc=otubo@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@redhat.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).