From: "Cho, Yu-Chen" <acho@suse.com>
To: marcel@holtmann.org, padovan@profusion.mobi,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: acho@novell.com, jlee@novell.com, oneukum@suse.com,
acho@suse.com, jlee@suse.com
Subject: [PATCH 2/3] fix device id for Broadcom SoftSailing
Date: Tue, 1 Nov 2011 17:33:06 +0800 [thread overview]
Message-ID: <441ba580885def5ff35d1172e265566c1870a60c.1320139612.git.acho@suse.com> (raw)
In-Reply-To: <944af9667334f5677be87e89fe8f38486823cc95.1320139612.git.acho@suse.com>
In-Reply-To: <944af9667334f5677be87e89fe8f38486823cc95.1320139612.git.acho@suse.com>
Fixed the device VID:PID typo 05ac:21e1 to 0a5c:21e1
Signed-off-by: Cho, Yu-Chen <acho@suse.com>
---
drivers/bluetooth/btusb.c | 5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index be01260..8583aee 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers/bluetooth/btusb.c
@@ -60,9 +60,6 @@ static struct usb_device_id btusb_table[] = {
/* Generic Bluetooth USB device */
{ USB_DEVICE_INFO(0xe0, 0x01, 0x01) },
- /* Broadcom SoftSailing reporting vendor specific */
- { USB_DEVICE(0x05ac, 0x21e1) },
-
/* Apple MacBookPro 7,1 */
{ USB_DEVICE(0x05ac, 0x8213) },
@@ -98,6 +95,8 @@ static struct usb_device_id btusb_table[] = {
{ USB_DEVICE(0x0bdb, 0x1002) },
/* Broadcom 20702 Bluetooth 4.0 Adapter */
+ /* Broadcom SoftSailing reporting vendor specific */
+ { USB_DEVICE(0x0a5c, 0x21e1) },
/* Broadcom Valentine 802.11bgn 1x1 Combo HMC */
{ USB_DEVICE(0x0a5c, 0x21e3) },
--
1.7.3.4
next prev parent reply other threads:[~2011-11-01 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 9:33 [PATCH 1/3] add device entry for Broadcom Valentine combo card Cho, Yu-Chen
2011-11-01 9:33 ` Cho, Yu-Chen [this message]
2011-11-01 9:33 ` [PATCH 3/3] add device entry for other Broadcom " Cho, Yu-Chen
2011-11-01 16:15 ` [PATCH 1/3] add device entry for Broadcom Valentine " Gustavo Padovan
2011-12-12 8:43 ` Al Cho
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=441ba580885def5ff35d1172e265566c1870a60c.1320139612.git.acho@suse.com \
--to=acho@suse.com \
--cc=acho@novell.com \
--cc=jlee@novell.com \
--cc=jlee@suse.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=oneukum@suse.com \
--cc=padovan@profusion.mobi \
/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
all inboxes | Powered by JetHome®