public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	Bastien Nocera <hadess@hadess.net>,
	Paul Menzel <pmenzel@molgen.mpg.de>,
	Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
	marcel@holtmann.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH AUTOSEL 4.14 8/8] Bluetooth: btusb: Fix quirks table naming
Date: Mon, 11 Sep 2023 11:40:07 +0200	[thread overview]
Message-ID: <ZP7gd93uo1qdKOTd@duo.ucw.cz> (raw)
In-Reply-To: <20230908182127.3461199-8-sashal@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]

Hi!

> 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.

Cleanup, not a bugfix. Don't need it in stable.

Best regards,
							Pavel

> +++ b/drivers/bluetooth/btusb.c
> @@ -186,7 +186,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 },
>  
> @@ -2963,7 +2963,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;
>  	}

-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2023-09-11 21:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-08 18:21 [PATCH AUTOSEL 4.14 1/8] wifi: ath9k: fix printk specifier Sasha Levin
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 2/8] wifi: mwifiex: fix fortify warning Sasha Levin
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 3/8] crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() Sasha Levin
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 4/8] tpm_tis: Resend command to recover from data transfer errors Sasha Levin
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 5/8] alx: fix OOB-read compiler warning Sasha Levin
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 6/8] netfilter: ebtables: fix fortify warnings in size_entry_mwt() Sasha Levin
2023-09-11  9:36   ` Pavel Machek
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 7/8] wifi: cfg80211: ocb: don't leave if not joined Sasha Levin
2023-09-11  9:38   ` Pavel Machek
2023-09-08 18:21 ` [PATCH AUTOSEL 4.14 8/8] Bluetooth: btusb: Fix quirks table naming Sasha Levin
2023-09-11  9:40   ` Pavel Machek [this message]

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=ZP7gd93uo1qdKOTd@duo.ucw.cz \
    --to=pavel@denx.de \
    --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=sashal@kernel.org \
    --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