Hi Scott, >> 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? they will be needed for kernels < 3.16 since that will be the earliest kernel this gets merged. The 3.15 merge window is closed for us. What you have with bluetooth-next/for-upstream is what is merged into 3.15 and from now on only bug fixes are allowed. 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
