linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santiago Carot-Nemesio <sancane@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Santiago Carot-Nemesio <sancane@gmail.com>
Subject: [PATCH 03/19] Unregister Health Thermometer Interface
Date: Tue, 20 Sep 2011 19:47:15 +0200	[thread overview]
Message-ID: <1316540841-14713-4-git-send-email-sancane@gmail.com> (raw)
In-Reply-To: <1316540841-14713-3-git-send-email-sancane@gmail.com>

---
 thermometer/thermometer.c |   23 ++++++++++++++++++++++-
 1 files changed, 22 insertions(+), 1 deletions(-)

diff --git a/thermometer/thermometer.c b/thermometer/thermometer.c
index a89d8a9..cdfe455 100644
--- a/thermometer/thermometer.c
+++ b/thermometer/thermometer.c
@@ -51,6 +51,17 @@ static void destroy_thermometer(gpointer user_data)
         g_free(t);
 }
 
+static gint cmp_device(gconstpointer a, gconstpointer b)
+{
+	const struct thermometer *t = a;
+	const struct btd_device *dev = b;
+
+	if (dev == t->dev)
+		return 0;
+
+	return -1;
+}
+
 static DBusMessage *get_properties(DBusConnection *conn, DBusMessage *msg,
 								void *data)
 {
@@ -143,5 +154,15 @@ int thermometer_register(DBusConnection *connection, struct btd_device *device,
 
 void thermometer_unregister(struct btd_device *device)
 {
-	/* TODO: Unregister Health Thermometer Interface */
+	struct thermometer *t;
+	GSList *l;
+
+	l = g_slist_find_custom(thermometers, device, cmp_device);
+	if (!l)
+		return;
+
+	t = l->data;
+	thermometers = g_slist_remove(thermometers, t);
+	g_dbus_unregister_interface(t->conn, device_get_path(t->dev),
+							THERMOMETER_INTERFACE);
 }
-- 
1.7.6.1


  reply	other threads:[~2011-09-20 17:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20 17:47 Health Thermomete Profile support Santiago Carot-Nemesio
2011-09-20 17:47 ` [PATCH 01/19] Get thermometer service range to load the driver Santiago Carot-Nemesio
2011-09-20 17:47   ` [PATCH 02/19] Register Health Thermometer Interface Santiago Carot-Nemesio
2011-09-20 17:47     ` Santiago Carot-Nemesio [this message]
2011-09-20 17:47       ` [PATCH 04/19] Add functions to manage attio callbacks Santiago Carot-Nemesio
2011-09-20 17:47         ` [PATCH 05/19] Add handler function to manage GATT indications Santiago Carot-Nemesio
2011-09-20 17:47           ` [PATCH 06/19] Get all characteristics in thermometer service Santiago Carot-Nemesio
2011-09-20 17:47             ` [PATCH 07/19] Read temperature type characteristic Santiago Carot-Nemesio
2011-09-20 17:47               ` [PATCH 08/19] Read measurement interval characteristic Santiago Carot-Nemesio
2011-09-20 17:47                 ` [PATCH 09/19] Set Intermediate property if intermediate temp. characteristic is supported Santiago Carot-Nemesio
2011-09-20 20:28                   ` Santiago Carot
2011-09-20 20:32               ` [PATCH 07/19] Read temperature type characteristic Gustavo Padovan
2011-09-20 20:40                 ` Santiago Carot
2011-09-20 20:46                   ` Gustavo Padovan
2011-09-20 20:53                     ` Santiago Carot

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=1316540841-14713-4-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).