From: Johan Hedberg <johan.hedberg@gmail.com>
To: Claudio Takahasi <claudio.takahasi@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 0/6] Proximity configs and LinkLoss alert write
Date: Wed, 3 Aug 2011 12:38:48 +0300 [thread overview]
Message-ID: <20110803093848.GC31600@dell> (raw)
In-Reply-To: <1311864173-16118-1-git-send-email-claudio.takahasi@openbossa.org>
Hi,
On Thu, Jul 28, 2011, Claudio Takahasi wrote:
> Dependency: "[PATCH BlueZ 0/5] Add Get/Set Property for Link Loss"
>
> Changes from the last series: ref counting inside Proximity Monitor based
> on the feedbacks/comments in the ML.
>
> The following patches implement the configuration file to allow
> disabling Proximity Monitor services and Find Me. First patch using
> attio connection callback registration mechanism to write Link Loss
> Alert level.
>
> Anderson Lizardo (1):
> Proximity Monitor: Write Alert Level to Reporter
>
> Claudio Takahasi (5):
> Add Tx Power and Immediate Alert UUID
> Add config file for proximity monitor
> Match probed UUIDs and enabled services
> Return an error if LinkLoss is disabled
> Return LinkLossAlertLevel if enabled
>
> Makefile.am | 4 +-
> proximity/main.c | 30 ++++++++++++-
> proximity/manager.c | 52 ++++++++++++++++++++--
> proximity/manager.h | 2 +-
> proximity/monitor.c | 109 ++++++++++++++++++++++++++++++++++++++++++++-
> proximity/monitor.h | 9 +++-
> proximity/proximity.conf | 9 ++++
> 7 files changed, 202 insertions(+), 13 deletions(-)
> create mode 100644 proximity/proximity.conf
This patch-set has also been applied. Thanks.
Johan
prev parent reply other threads:[~2011-08-03 9:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 21:53 [PATCH BlueZ 0/6] Proximity configs and LinkLoss alert write Claudio Takahasi
2011-07-27 21:53 ` [PATCH BlueZ 1/6] Proximity Monitor: Write Alert Level to Reporter Claudio Takahasi
2011-07-28 4:40 ` Santiago Carot
[not found] ` <CACLukz+g-994zKLK1aPkBusEhv=ti850KhMSjGZQjJOdL9kdcw@mail.gmail.com>
2011-07-28 13:05 ` Claudio Takahasi
2011-07-28 13:12 ` Johan Hedberg
2011-07-28 14:43 ` [PATCH BlueZ v2 " Claudio Takahasi
2011-07-27 21:53 ` [PATCH BlueZ 2/6] Add Tx Power and Immediate Alert UUID Claudio Takahasi
2011-07-28 14:43 ` [PATCH BlueZ v2 " Claudio Takahasi
2011-07-27 21:53 ` [PATCH BlueZ 3/6] Add config file for proximity monitor Claudio Takahasi
2011-07-28 14:43 ` [PATCH BlueZ v2 " Claudio Takahasi
2011-07-27 21:53 ` [PATCH BlueZ 4/6] Match probed UUIDs and enabled services Claudio Takahasi
2011-07-28 14:43 ` [PATCH BlueZ v2 " Claudio Takahasi
2011-07-27 21:53 ` [PATCH BlueZ 5/6] Return an error if LinkLoss is disabled Claudio Takahasi
2011-07-28 14:43 ` [PATCH BlueZ v2 " Claudio Takahasi
2011-07-27 21:53 ` [PATCH BlueZ 6/6] Return LinkLossAlertLevel if enabled Claudio Takahasi
2011-07-28 14:43 ` [PATCH BlueZ v2 " Claudio Takahasi
2011-07-28 14:42 ` [PATCH BlueZ v2 0/6] Proximity configs and LinkLoss alert write Claudio Takahasi
2011-08-03 9:38 ` 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=20110803093848.GC31600@dell \
--to=johan.hedberg@gmail.com \
--cc=claudio.takahasi@openbossa.org \
--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).