From: Johan Hedberg <johan.hedberg@gmail.com>
To: Emeltchenko Andrei <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH hcidump v2] hcidump: parse extended control field in l2cap
Date: Tue, 27 Sep 2011 16:36:57 +0300 [thread overview]
Message-ID: <20110927133657.GA9071@dell> (raw)
In-Reply-To: <1317127529-15094-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
Hi Andrei,
On Tue, Sep 27, 2011, Emeltchenko Andrei wrote:
> Adds support for parsing extended control field. Extended control
> field may be used for ERTM and streaming mode (if EWS specified).
> ext_ctrl flag resides in cid table, added fixes for P-bit decode.
> ---
> parser/l2cap.c | 140 ++++++++++++++++++++++++++++++++++++++++++++-----------
> 1 files changed, 112 insertions(+), 28 deletions(-)
Both patches have been applied. Thanks.
Johan
prev parent reply other threads:[~2011-09-27 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 12:45 [PATCH hcidump v2] hcidump: parse extended control field in l2cap Emeltchenko Andrei
2011-09-27 12:50 ` Emeltchenko Andrei
2011-09-27 13:04 ` Emeltchenko Andrei
2011-09-27 13:36 ` 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=20110927133657.GA9071@dell \
--to=johan.hedberg@gmail.com \
--cc=Andrei.Emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).