From: Heiner Kallweit <hkallweit1@gmail.com>
To: "Clément de l'Hamaide" <clement.delhamaide@gmail.com>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0
Date: Fri, 5 Feb 2016 19:50:39 +0100 [thread overview]
Message-ID: <56B4EEFF.1000603@gmail.com> (raw)
In-Reply-To: <CAG4Y7ev8wYnKyrTp-3QAP7O17ypAU9PYBD_QJdcR-8bPLZ=xCw@mail.gmail.com>
Hi Clement,
Am 05.02.2016 um 13:12 schrieb Clément de l'Hamaide:
> Hi,
>
> Some months ago I posted a patch.
> I can see some people around internet reporting 0cf3:3004 not working
> then I realized that my patch have not been reviewed/commited.
>
> My bluetooth is working well since end of October with my patch.
> I'm sure Linux users who have this hardware would be thanksful if my
> patch is reviewed and commited.
>
chances for review would be higher if you keep to the formal criteria
for patches. Please have a look at Documentation/SubmittingPatches.
Things to improve:
- replace subject with a a proper description of the patch including
appropriate module prefix
- add patch description
- address patch to maintainer + list on cc
>
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index b6aceaf..884dbe5 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -199,7 +199,6 @@ static const struct usb_device_id blacklist_table[] = {
> { USB_DEVICE(0x0930, 0x0227), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x0036), .driver_info = BTUSB_ATH3012 },
> - { USB_DEVICE(0x0cf3, 0x3004), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x3008), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x311d), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0cf3, 0x311e), .driver_info = BTUSB_ATH3012 },
> @@ -230,6 +229,7 @@ static const struct usb_device_id blacklist_table[] = {
> { USB_DEVICE(0x0cf3, 0xe007), .driver_info = BTUSB_QCA_ROME },
> { USB_DEVICE(0x0cf3, 0xe300), .driver_info = BTUSB_QCA_ROME },
> { USB_DEVICE(0x0cf3, 0xe360), .driver_info = BTUSB_QCA_ROME },
> + { USB_DEVICE(0x0cf3, 0x3004), .driver_info = BTUSB_QCA_ROME },
>
> /* Broadcom BCM2035 */
> { USB_DEVICE(0x0a5c, 0x2009), .driver_info = BTUSB_BCM92035 },
>
>
>
> Regards,
> Clément
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2016-02-05 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 12:12 [PATCH] 0cf3:3004 Atheros Communications, Inc. AR3012 Bluetooth 4.0 Clément de l'Hamaide
2016-02-05 18:50 ` Heiner Kallweit [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=56B4EEFF.1000603@gmail.com \
--to=hkallweit1@gmail.com \
--cc=clement.delhamaide@gmail.com \
--cc=linux-bluetooth@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 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.