From: Johan Hedberg <johan.hedberg@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 1/5 v2] AVRCP: use a vtable to simplify PDU parsing/handling
Date: Tue, 27 Sep 2011 11:30:23 +0300 [thread overview]
Message-ID: <20110927083023.GI3952@dell> (raw)
In-Reply-To: <1315845241-17077-1-git-send-email-luiz.dentz@gmail.com>
Hi Luiz,
On Mon, Sep 12, 2011, Luiz Augusto von Dentz wrote:
> This simplify a bit the handling by introducing common checks before
> calling the handler callback, it is also much easier to add/remove
> new PDUs in this way.
> ---
> audio/control.c | 321 +++++++++++++++++++++----------------------------------
> 1 files changed, 124 insertions(+), 197 deletions(-)
All five patches applied. Thanks.
Johan
prev parent reply other threads:[~2011-09-27 8:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 16:33 [PATCH BlueZ 1/5 v2] AVRCP: use a vtable to simplify PDU parsing/handling Luiz Augusto von Dentz
2011-09-12 16:33 ` [PATCH BlueZ 2/5 v2] AVRCP: rename avrcp_header to avc_header Luiz Augusto von Dentz
2011-09-12 18:01 ` Lucas De Marchi
2011-09-12 16:33 ` [PATCH BlueZ 3/5 v2] AVRCP: rename avrcp_spec_avc_pdu to avrcp_header Luiz Augusto von Dentz
2011-09-12 16:34 ` [PATCH BlueZ 4/5 v2] AVRCP: split AVCTP specific code from control.c Luiz Augusto von Dentz
[not found] ` <73958080.14803.1315928807132.JavaMail.open-xchange@oxusltgw08.schlund.de>
2011-09-14 9:12 ` Luiz Augusto von Dentz
2011-09-12 16:34 ` [PATCH BlueZ 5/5 v2] AVRCP: move handling of vendor dependent PDU from control.c to avrcp.c Luiz Augusto von Dentz
2011-09-12 17:57 ` [PATCH BlueZ 1/5 v2] AVRCP: use a vtable to simplify PDU parsing/handling Lucas De Marchi
2011-09-27 8:30 ` Johan Hedberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110927083023.GI3952@dell \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.