From: Peter Krystad <pkrystad@codeaurora.org>
To: linux-bluetooth@vger.kernel.org
Cc: johan.hedberg@gmail.com, Peter Krystad <pkrystad@codeaurora.org>
Subject: [PATCH v4 0/5] Add parsing of BT 3.0+HS signals
Date: Wed, 15 Feb 2012 11:04:10 -0800 [thread overview]
Message-ID: <1329332655-27394-1-git-send-email-pkrystad@codeaurora.org> (raw)
v4 - Content unchanged but A2MP definitions added to own file
Sending again after reading the send-email prompts more carefully...
Peter Krystad (5):
Add L2CAP Create/Move Channel definitions
Add A2MP definitions
Add parsing of L2CAP Create/Move Channel signals
Add parsing of A2MP signals
Minor indentation cleanup and fix display of physical link key
Makefile.am | 2 +-
lib/a2mp.h | 115 ++++++++++++++
lib/l2cap.h | 45 ++++++
parser/hci.c | 15 ++-
parser/l2cap.c | 450 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
parser/parser.h | 1 +
src/hcidump.c | 1 +
7 files changed, 623 insertions(+), 6 deletions(-)
--
1.7.4.1
--
Peter Krystad
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next reply other threads:[~2012-02-15 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 19:04 Peter Krystad [this message]
2012-02-15 19:04 ` [PATCH v4 1/5] Add L2CAP Create/Move Channel definitions Peter Krystad
2012-03-01 1:34 ` Johan Hedberg
2012-02-15 19:04 ` [PATCH v4 2/5] Add A2MP definitions Peter Krystad
2012-02-15 19:04 ` [PATCH v4 3/5] Add parsing of L2CAP Create/Move Channel signals Peter Krystad
2012-02-15 19:04 ` [PATCH v4 4/5] Add parsing of A2MP signals Peter Krystad
2012-02-15 19:04 ` [PATCH v4 5/5] Minor indentation cleanup and fix display of physical link key Peter Krystad
-- strict thread matches above, loose matches on Subject: below --
2012-02-15 1:09 [PATCH v4 0/5] Add parsing of BT 3.0+HS signals y
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=1329332655-27394-1-git-send-email-pkrystad@codeaurora.org \
--to=pkrystad@codeaurora.org \
--cc=johan.hedberg@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).