public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Bastien Nocera <hadess@hadess.net>,
	Paul Menzel <pmenzel@molgen.mpg.de>,
	Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
	Sasha Levin <sashal@kernel.org>,
	marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org
Subject: [PATCH AUTOSEL 5.4 10/10] Bluetooth: btusb: Fix quirks table naming
Date: Fri,  8 Sep 2023 14:20:44 -0400	[thread overview]
Message-ID: <20230908182046.3460968-10-sashal@kernel.org> (raw)
In-Reply-To: <20230908182046.3460968-1-sashal@kernel.org>

From: Bastien Nocera <hadess@hadess.net>

[ Upstream commit d831e3612111d385e8629104af5429808ef26e25 ]

The quirks table was named "blacklist_table" which isn't a good
description for that table as devices detected using it weren't ignored
by the driver.

Rename the table to match what it actually does.

Signed-off-by: Bastien Nocera <hadess@hadess.net>
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
 drivers/bluetooth/btusb.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 79f77315854f4..c766861b65573 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -170,7 +170,7 @@ static const struct usb_device_id btusb_table[] = {
 
 MODULE_DEVICE_TABLE(usb, btusb_table);
 
-static const struct usb_device_id blacklist_table[] = {
+static const struct usb_device_id quirks_table[] = {
 	/* CSR BlueCore devices */
 	{ USB_DEVICE(0x0a12, 0x0001), .driver_info = BTUSB_CSR },
 
@@ -3620,7 +3620,7 @@ static int btusb_probe(struct usb_interface *intf,
 	if (!id->driver_info) {
 		const struct usb_device_id *match;
 
-		match = usb_match_id(intf, blacklist_table);
+		match = usb_match_id(intf, quirks_table);
 		if (match)
 			id = match;
 	}
-- 
2.40.1


  parent reply	other threads:[~2023-09-08 19:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 18:20 [PATCH AUTOSEL 5.4 01/10] devlink: remove reload failed checks in params get/set callbacks Sasha Levin
2023-09-08 18:20 ` [PATCH AUTOSEL 5.4 02/10] wifi: ath9k: fix printk specifier Sasha Levin
2023-09-08 18:20 ` [PATCH AUTOSEL 5.4 03/10] wifi: mwifiex: fix fortify warning Sasha Levin
2023-09-08 18:20 ` [PATCH AUTOSEL 5.4 04/10] crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() Sasha Levin
2023-09-08 18:20 ` [PATCH AUTOSEL 5.4 05/10] tpm_tis: Resend command to recover from data transfer errors Sasha Levin
2023-09-08 18:20 ` [PATCH AUTOSEL 5.4 06/10] mmc: sdhci-esdhc-imx: improve ESDHC_FLAG_ERR010450 Sasha Levin
2023-09-08 18:20 ` [PATCH AUTOSEL 5.4 07/10] alx: fix OOB-read compiler warning Sasha Levin
2023-09-08 18:20 ` [PATCH AUTOSEL 5.4 08/10] wifi: mac80211_hwsim: drop short frames Sasha Levin
2023-09-08 18:20 ` [PATCH AUTOSEL 5.4 09/10] libbpf: Free btf_vmlinux when closing bpf_object Sasha Levin
2023-09-08 18:20 ` Sasha Levin [this message]
2023-09-08 21:11 ` [PATCH AUTOSEL 5.4 01/10] devlink: remove reload failed checks in params get/set callbacks Jacob Keller

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=20230908182046.3460968-10-sashal@kernel.org \
    --to=sashal@kernel.org \
    --cc=hadess@hadess.net \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=luiz.von.dentz@intel.com \
    --cc=marcel@holtmann.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=stable@vger.kernel.org \
    /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