Hi Scott, On Fri, Apr 04, 2014, Scott James Remnant wrote: > On Fri, Apr 4, 2014 at 12:25 AM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > > > One thing to note regarding this first one: this is actually not a > > problem with current bluetooth-next since there we merge the adv_ind and > > scan_rsp into a single mgmt device found event. I.e. with such a kernel > > we will not need to have this extra non-zero flags check. I added an > > extra code comment to this place so we don't forget to fix it. > > > > Makes sense, we're testing with the current > bluetooth-next/for-upstream tag, and it looks like the > ADV_IND/SCAN_RSP merging patches aren't submitted yet ;-) > > Won't this mean that the flag checking will be needed on kernels prior > to 3.15 in either case? Correct. Prior to 3.16 actually since that's where the merging patches will land. Once we know the mgmt revision that 3.16 will have (probably the current one + 1) we can add a check for this to the user space code. Johan -- 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
