All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Gustavo F. Padovan" <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	linux-bluetooth@vger.kernel.org, stable@vger.kernel.org,
	Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH] Revert "Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174"
Date: Fri, 27 Apr 2018 10:49:52 +0200	[thread overview]
Message-ID: <a4ba16ef-6369-fe32-24e0-30efb27a63f3@redhat.com> (raw)
In-Reply-To: <009e5572-3766-f634-43be-7a3fce9ccfd8@redhat.com>

Hi,

On 26-04-18 20:28, Hans de Goede wrote:
> Hi,
> 
> On 26-04-18 14:22, Marcel Holtmann wrote:
>> Hi Hans,
>>
>>> Commit f44cb4b19ed4 ("Bluetooth: btusb: Fix quirk for Atheros
>>> 1525/QCA6174") is causing bluetooth to no longer work for several
>>> people, see: https://bugzilla.redhat.com/show_bug.cgi?id=1568911
>>>
>>> So lets revert it for now and try to find another solution for
>>> devices which need the modified quirk.
>>>
>>> Cc: stable@vger.kernel.org
>>> Cc: Takashi Iwai <tiwai@suse.de>
>>> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
>>> ---
>>> drivers/bluetooth/btusb.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> patch has been applied to bluetooth-next tree.
> 
> This is a regression fix, so can we please get this into 4.17-rc#
> so that Greg can then take it into 4.16.z ?

Also see: https://bugzilla.kernel.org/show_bug.cgi?id=199271

Regards,

Hans

  reply	other threads:[~2018-04-27  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 12:18 [PATCH] Revert "Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174" Hans de Goede
2018-04-26 12:22 ` Marcel Holtmann
2018-04-26 18:28   ` Hans de Goede
2018-04-27  8:49     ` Hans de Goede [this message]
2018-04-27 16:35       ` Marcel Holtmann

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=a4ba16ef-6369-fe32-24e0-30efb27a63f3@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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.