On Fri, 2017-11-10 at 06:23 +0100, Bastien Nocera wrote: > When a reconnect timeout has previously run for a device, setting a > new > one will throw a warning as the timeout id is not reset when the > timeout > is cancelled from within its callback. Note that this is the 2nd patch I send with the same subject. They're not the same patches, and fix 2 different bugs in that part of the code. Cheers -- 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
