From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
To: Peter Krystad <pkrystad@codeaurora.org>, johan.hedberg@gmail.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv3 0/4] Add BT 3.0+HS parsing
Date: Wed, 4 Jan 2012 12:18:44 +0200 [thread overview]
Message-ID: <20120104101842.GD16309@aemeltch-MOBL1> (raw)
In-Reply-To: <1323756157-15487-1-git-send-email-pkrystad@codeaurora.org>
Hi,
On Mon, Dec 12, 2011 at 10:02:33PM -0800, Peter Krystad wrote:
> This patch adds parsing and display of BT 3.0+HS signalling
>
> v3 - same content but A2MP definitions placed in l2cap.h
Looks OK, despite I would not mix typedefs and normal structs in one
patch (maybe we can even remove typedefs later).
Johan, as definitions moved to existing header, hence without modifying
license can these patches be applied?
Best regards
Andrei Emeltchenko
>
> Peter Krystad (4):
> Add L2CAP Create/Move channel and A2MP definitions
> Add parsing of L2CAP Create/Move Channel signals
> Add parsing of A2MP signals
> Minor cleanup of indentation in output
>
> lib/l2cap.h | 159 +++++++++++++++++++-
> parser/hci.c | 15 ++-
> parser/l2cap.c | 449 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> parser/parser.h | 1 +
> src/hcidump.c | 1 +
> 5 files changed, 619 insertions(+), 6 deletions(-)
>
prev parent reply other threads:[~2012-01-04 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 6:02 [PATCHv3 0/4] Add BT 3.0+HS parsing Peter Krystad
2011-12-13 6:02 ` [PATCHv3 1/4] Add L2CAP Create/Move channel and A2MP definitions Peter Krystad
2011-12-13 6:02 ` [PATCHv3 2/4] Add parsing of L2CAP Create/Move Channel signals Peter Krystad
2011-12-13 6:02 ` [PATCHv3 3/4] Add parsing of A2MP signals Peter Krystad
2011-12-13 6:02 ` [PATCHv3 4/4] Minor cleanup of indentation in output Peter Krystad
2012-01-04 10:18 ` Andrei Emeltchenko [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=20120104101842.GD16309@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pkrystad@codeaurora.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