Hi Vani,
On Fri, Aug 3, 2012 at 12:43 PM, Vani-dineshbhai PATEL
<vani.patel@xxxxxxxxxxxxxx> wrote:
> +unsigned int avctp_register_browsing_pdu_handler(avctp_browsing_pdu_cb cb,
> + void *user_data)
> +{
> + static unsigned int id = 0;
> +
> + browsing_handler = g_new(struct avctp_browsing_pdu_handler, 1);
> + browsing_handler->cb = cb;
> + browsing_handler->user_data = user_data;
> + browsing_handler->id = ++id;
> +
> + return browsing_handler->id;
> +}
If we can only have a single pdu handler there is probably no need to
have an id assigned, but I thought the idea was to reuse
avctp_register_pdu_handler with something outside of the range of
control opcodes e.g. > 0xFF.
--
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
