Hi Marcel, On Fri, Jan 11, 2013 at 10:47 PM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > Hi Luiz, > >> This is convenient as some callbacks don't provide the client which >> the proxy belongs. > > and I did not add that one on purpose. You should know where your proxy > belongs to and worst case hand it over via user_data. I understand this as the user_data will always be the client pointer, or a struct containing it, or you have to use a global variable, is that what you really want? The use application has given the client when registering the callbacks, so it is already passing it as context. Now that being said, Im not saying the design utterly broken, quite the contrary it work like a charm, it just could be more convenient and that is what Im trying to achieve with this patch. -- 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
