From: Dmitry Tunin <hanipouspilot@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ath3k: Revert 7e730c7f3d1f39c25cf5f7cf70c0ff4c28d7bec7
Date: Tue, 11 Aug 2015 15:52:44 +0300 [thread overview]
Message-ID: <55C9F01C.4010805@gmail.com> (raw)
In-Reply-To: <1439290229-6937-1-git-send-email-hanipouspilot@gmail.com>
11.08.2015 13:50, Dmitry Tunin пишет:
> This patch causes infinite loop on loading firmware on Acer Aspire
> V3è371-31KW and probably other laptops.
>
> This is a serious regression, because system becomes unresponsive.
>
> This should be reverted until the firmware loading issue is sorted out.
>
> Signed-off-by: Dmitry Tunin <hanipouspilot@gmail.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/bluetooth/ath3k.c | 2 --
> drivers/bluetooth/btusb.c | 1 -
> 2 files changed, 3 deletions(-)
>
> diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
> index e527a3e..2fa6588 100644
> --- a/drivers/bluetooth/ath3k.c
> +++ b/drivers/bluetooth/ath3k.c
> @@ -89,7 +89,6 @@ static const struct usb_device_id ath3k_table[] = {
> { USB_DEVICE(0x04CA, 0x3007) },
> { USB_DEVICE(0x04CA, 0x3008) },
> { USB_DEVICE(0x04CA, 0x300b) },
> - { USB_DEVICE(0x04CA, 0x300d) },
> { USB_DEVICE(0x04CA, 0x300f) },
> { USB_DEVICE(0x04CA, 0x3010) },
> { USB_DEVICE(0x0930, 0x0219) },
> @@ -149,7 +148,6 @@ static const struct usb_device_id ath3k_blist_tbl[] = {
> { USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
> - { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x04ca, 0x300f), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x04ca, 0x3010), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
> diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
> index cc92b0f..73e3b7c 100644
> --- a/drivers/bluetooth/btusb.c
> +++ b/drivers/bluetooth/btusb.c
> @@ -191,7 +191,6 @@ static const struct usb_device_id blacklist_table[] = {
> { USB_DEVICE(0x04ca, 0x3007), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x04ca, 0x3008), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x04ca, 0x300b), .driver_info = BTUSB_ATH3012 },
> - { USB_DEVICE(0x04ca, 0x300d), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x04ca, 0x300f), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x04ca, 0x3010), .driver_info = BTUSB_ATH3012 },
> { USB_DEVICE(0x0930, 0x0219), .driver_info = BTUSB_ATH3012 },
>
I just got a response that kernel 4.2rc6 is affected by this regression.
next prev parent reply other threads:[~2015-08-11 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 10:50 [PATCH] ath3k: Revert 7e730c7f3d1f39c25cf5f7cf70c0ff4c28d7bec7 Dmitry Tunin
2015-08-11 12:52 ` Dmitry Tunin [this message]
2015-08-11 19:23 ` Marcel Holtmann
2015-08-11 19:43 ` Dmitry Tunin
2015-08-11 19:54 ` Dmitry Tunin
2015-08-11 19:59 ` Dmitry Tunin
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=55C9F01C.4010805@gmail.com \
--to=hanipouspilot@gmail.com \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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;
as well as URLs for NNTP newsgroup(s).