Hi Tim, >> I actually need to know if bluetooth-next tree still has this issue. That is first and foremost the one thing that needs to be checked. > > I really doubt it's an issue with bluetooth-next as it's only been an issue with kernel versions 3.4.X and older. > > I'm not familiar with how kernel development goes, so I'm not sure I completely understand what "bluetooth-next" entails. Aren't there different maintainers for the different major versions of the kernel and don't they update the in-built modules where ever possible? Is "bluetooth-next" tied to a particular kernel version or does it support a range of versions as it's a module? bluetooth-next is what will become kernel 3.13 at some point when Linus releases it. It is code that is on its way towards official Linux trees. If bluetooth-next works as expected, then you could just git bisect and root cause the patch that fixed it. However first you have to establish if bluetooth-next kernel works or not. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
