Hi, I suggest at some point grabbing your company management and having them book a meeting or two with QCA. That's how resources get assigned to this. Otherwise Sujith is doing it when he can and he's already burnt out at the best of times.. :-)
-a On 3 January 2014 09:12, Joshua Richenhagen <richenha...@gmail.com> wrote: > Today the Canonical Kernel Team has build a test kernel from the > upstream linux-next tree for me (based on 3.13-rc5). This kernel > includes the latest bluetooth stack, including your patch. But sadly > it still doesn't work and dmesg shows the same error message I already > reported. > > Full dmesg output: http://paste.ubuntu.com/6685680/ > > Is there anything further I could do to help the bluetooth devs > finding the cause? > > > > 2013/12/13 Sujith Manoharan <suj...@msujith.org>: >> Joshua Richenhagen wrote: >>> Dear Sujith, >>> >>> I was just wondering that the patch still didn't landed upstream until >>> 3.13-rc3. Are you holding the patch back until the firmware bug is >>> solved? >> >> The patch has been merged in bluetooth-next: >> https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=35580d223b6b04d9a570e4fe377c46a102413fe8 >> >> Sujith > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
