From: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
Subject: [RFC_v2 0/6] HDP initial implementaion
Date: Tue, 10 Jun 2014 16:21:57 +0300 [thread overview]
Message-ID: <1402406523-2832-1-git-send-email-ravikumar.veeramally@linux.intel.com> (raw)
v2: Fixed comments by szymon and fixed issues while sebastian
testing with PTS.
v1: patchset is initial implementaion for HDP at daemon side.
Cacheing application data and prepare SDP record based on MDEPs
configuration and notify app state.
Ravi kumar Veeramally (6):
android/hal-ipc-txt: Update Health MDEP command parameter
android/health: Fix MDEP data type is 2 octets
android/health: Cache health application data on app register call
android/health: Perform clean up on app unregister call
android/health: Add HDP SDP record
android/health: Notify application registration status
android/hal-ipc-api.txt | 5 +-
android/hal-msg.h | 2 +-
android/health.c | 712 +++++++++++++++++++++++++++++++++++++++++++++++-
3 files changed, 707 insertions(+), 12 deletions(-)
--
1.8.3.2
next reply other threads:[~2014-06-10 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 13:21 Ravi kumar Veeramally [this message]
2014-06-10 13:21 ` [RFC_v2 1/6] android/hal-ipc-txt: Update Health MDEP command parameter Ravi kumar Veeramally
2014-06-10 13:21 ` [RFC_v2 2/6] android/health: Fix MDEP data type is 2 octets Ravi kumar Veeramally
2014-06-10 13:22 ` [RFC_v2 3/6] android/health: Cache health application data on app register call Ravi kumar Veeramally
2014-06-10 13:22 ` [RFC_v2 4/6] android/health: Perform clean up on app unregister call Ravi kumar Veeramally
2014-06-10 13:22 ` [RFC_v2 5/6] android/health: Add HDP SDP record Ravi kumar Veeramally
2014-06-10 13:22 ` [RFC_v2 6/6] android/health: Notify application registration status Ravi kumar Veeramally
2014-06-12 10:10 ` [RFC_v2 0/6] HDP initial implementaion Szymon Janc
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=1402406523-2832-1-git-send-email-ravikumar.veeramally@linux.intel.com \
--to=ravikumar.veeramally@linux.intel.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