Hi Mikel, On Tue, Dec 13, 2011, Mikel Astiz 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. > --- > gobex/gobex-transfer.c | 30 +++++++++++++++++++----------- > 1 files changed, 19 insertions(+), 11 deletions(-) Applied. Thanks. 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
