From: Santiago Carot-Nemesio <sancane@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Health Thermometer Profile patches
Date: Fri, 9 Dec 2011 19:18:58 +0100 [thread overview]
Message-ID: <1323454744-14589-1-git-send-email-sancane@gmail.com> (raw)
This is a new set of patches wich implement most of the features in
HTP. GATT reconnections are the only missing feature up to now.
These patches depend on the patch:
att.h: Add client characteristic configuration bit fields
Changes include next patches:
[PATCH 1/6] thermometer.c: Implement SetProperty D-Bus method
[PATCH 2/6] thermometer.c: Confiure C.C.C descriptor during the
[PATCH 3/6] thermometer.c: Process measurement interval indications
[PATCH 4/6] thermometer.c: Fix possible null pointer deference
[PATCH 5/6] thermometer.c: Fix bad read operation when time stamp isn't provided
[PATCH 6/6] thermometer.c: Use system types instead of GLIB ones.
next reply other threads:[~2011-12-09 18:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 18:18 Santiago Carot-Nemesio [this message]
2011-12-09 18:18 ` [PATCH 1/6] thermometer.c: Implement SetProperty D-Bus method Santiago Carot-Nemesio
2011-12-09 18:19 ` [PATCH 2/6] thermometer.c: Confiure C.C.C descriptor during the thermometer configuration Santiago Carot-Nemesio
2011-12-09 18:19 ` [PATCH 3/6] thermometer.c: Process measurement interval indications Santiago Carot-Nemesio
2011-12-09 18:19 ` [PATCH 4/6] thermometer.c: Fix possible null pointer deference Santiago Carot-Nemesio
2011-12-09 18:19 ` [PATCH 5/6] thermometer.c: Fix bad read operation when time stamp is not provided Santiago Carot-Nemesio
2011-12-09 18:19 ` [PATCH 6/6] thermometer.c: Use system types instead of GLIB ones Santiago Carot-Nemesio
2011-12-15 11:29 ` Health Thermometer Profile patches Johan Hedberg
-- strict thread matches above, loose matches on Subject: below --
2011-11-22 14:49 Santiago Carot-Nemesio
2011-09-29 13:46 Santiago Carot-Nemesio
2011-09-28 17:48 Santiago Carot-Nemesio
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=1323454744-14589-1-git-send-email-sancane@gmail.com \
--to=sancane@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).