All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Peng Chen <pengchen@qti.qualcomm.com>,
	"Gustavo F. Padovan" <gustavo@padovan.org>,
	Linux Bluetooth mailing list <linux-bluetooth@vger.kernel.org>,
	kumo@qca.qualcomm.com, taowang@qti.qualcomm.com
Subject: Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012.
Date: Tue, 08 Jul 2014 12:49:07 +0200	[thread overview]
Message-ID: <53BBCCA3.9040706@ahsoftware.de> (raw)
In-Reply-To: <D0167450-1E5D-49A1-8D49-6D6AC528C463@holtmann.org>

Am 08.07.2014 12:35, schrieb Marcel Holtmann:
> Hi Alexander,
>
>>>> which is wrong and disables the ath3k driver.
>>>
>>> I reverted the broken patch in bluetooth.git now and marked it for 3.15 stable.
>>
>> Must got missed, it's not in 3.15.4 nor in 3.15.5.
>>
>> As my solution was a revert too, I can offer a Tested-By, if such is needed, at least in regard to the point that ath3k-dongles will work again after reverting ca58e5.
>
> it is in net tree, but not in 3.16-rcX yet. Only after it got into Linus' tree it can be backported to stable tree.

Ah, the funny maze of linux kernel repos. ;)

I've just wondered because I've seen several bluetooth related patches 
in 3.15.5 and therefor got the impression it got missed.

Regards,

Alexander Holler

  reply	other threads:[~2014-07-08 10:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30  9:09 [PATCH] Add a new PID/VID 0cf3/e005 for AR3012 Peng Chen
2014-03-05 18:59 ` Johan Hedberg
2014-06-20 10:01 ` Alexander Holler
2014-06-20 10:50   ` Marcel Holtmann
2014-07-08  7:31     ` Alexander Holler
2014-07-08 10:35       ` Marcel Holtmann
2014-07-08 10:49         ` Alexander Holler [this message]
2014-07-09 10:48           ` Alexander Holler
2014-07-09 11:05             ` Marcel Holtmann
2014-07-09 11:21               ` Alexander Holler
2014-07-09 11:47                 ` Alexander Holler
  -- strict thread matches above, loose matches on Subject: below --
2013-08-30  9:41 Peng Chen
2013-09-01 16:50 ` Gustavo Padovan

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=53BBCCA3.9040706@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --cc=gustavo@padovan.org \
    --cc=kumo@qca.qualcomm.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=pengchen@qti.qualcomm.com \
    --cc=taowang@qti.qualcomm.com \
    /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.