Hi Mikel, On Tue, Dec 13, 2011 at 6:21 PM, Mikel Astiz <mikel.astiz@xxxxxxxxxxxx> wrote: > The previous approach searched the transfer pointer itself, assuming > that the transfers has not been modified if the pointer is in the list. > However the callback could have removed the transfer and registered > another one, which can eventually point to the same memory location. > > This is solved by looking for the transfer id instead of the pointer. > --- Ack. -- Luiz Augusto von Dentz -- 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
