All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Schulz <paul@mawsonlakes.org>
To: alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.com>, Paul Schulz <paul@mawsonlakes.org>
Subject: [PATCH] sound/soc/soc-core: Removed instances of 'blacklist'
Date: Thu, 16 Jul 2020 02:18:36 +0930	[thread overview]
Message-ID: <20200715164836.123012-1-paul@mawsonlakes.org> (raw)

This patch removes 'blacklist' and replaces it with
'invalid list' in sound/soc/soc-core.c

This is a functionally trivial patch and has no other effect.

Signed-off-by: Paul Schulz <paul@mawsonlakes.org>
---
 sound/soc/soc-core.c | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c
index 0f30f5aabaa8..6bc56c4cb207 100644
--- a/sound/soc/soc-core.c
+++ b/sound/soc/soc-core.c
@@ -1457,11 +1457,11 @@ EXPORT_SYMBOL_GPL(snd_soc_runtime_set_dai_fmt);
 
 #ifdef CONFIG_DMI
 /*
- * If a DMI filed contain strings in this blacklist (e.g.
+ * If a DMI filed contain strings in this invalid list (e.g.
  * "Type2 - Board Manufacturer" or "Type1 - TBD by OEM"), it will be taken
  * as invalid and dropped when setting the card long name from DMI info.
  */
-static const char * const dmi_blacklist[] = {
+static const char * const dmi_invalid_list[] = {
 	"To be filled by OEM",
 	"TBD by OEM",
 	"Default String",
@@ -1493,14 +1493,14 @@ static void cleanup_dmi_name(char *name)
 
 /*
  * Check if a DMI field is valid, i.e. not containing any string
- * in the black list.
+ * in the invalid list.
  */
 static int is_dmi_valid(const char *field)
 {
 	int i = 0;
 
-	while (dmi_blacklist[i]) {
-		if (strstr(field, dmi_blacklist[i]))
+	while (dmi_invalid_list[i]) {
+		if (strstr(field, dmi_invalid_list[i]))
 			return 0;
 		i++;
 	}
-- 
2.25.1


                 reply	other threads:[~2020-07-16  7:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200715164836.123012-1-paul@mawsonlakes.org \
    --to=paul@mawsonlakes.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.