From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <53BD1DF2.7060607@ahsoftware.de> Date: Wed, 09 Jul 2014 12:48:18 +0200 From: Alexander Holler MIME-Version: 1.0 To: Marcel Holtmann CC: Peng Chen , "Gustavo F. Padovan" , Linux Bluetooth mailing list , kumo@qca.qualcomm.com, taowang@qti.qualcomm.com Subject: Re: [PATCH] Add a new PID/VID 0cf3/e005 for AR3012. References: <1377853792-17589-1-git-send-email-pengchen@qca.qualcomm.com> <53A40687.80004@ahsoftware.de> <850D59CB-8032-4095-AB96-61920042DC55@holtmann.org> <53BB9E5F.9020101@ahsoftware.de> <53BBCCA3.9040706@ahsoftware.de> In-Reply-To: <53BBCCA3.9040706@ahsoftware.de> Content-Type: text/plain; charset=us-ascii; format=flowed List-ID: Am 08.07.2014 12:49, schrieb Alexander Holler: > 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. ;) That lead me to the idea to rename bluetooth-next to bluetooth-ubernext because that what be more appropriate if bluetooth-next ends up in net-next or linux-next or something-else-next. ;) Sorry for the joke. ;) Regards, Alexander Holler