linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anderson Lizardo <anderson.lizardo@openbossa.org>
To: linux-bluetooth@vger.kernel.org
Cc: Anderson Lizardo <anderson.lizardo@openbossa.org>
Subject: [PATCH BlueZ] proximity: Fix Proximity API to match documentation
Date: Fri,  3 Feb 2012 09:42:56 -0400	[thread overview]
Message-ID: <1328276576-2996-1-git-send-email-anderson.lizardo@openbossa.org> (raw)

Recently, the documented D-Bus interface for Proximity was changed to
prepare for the upcoming Proximity Reporter API.
---
 proximity/monitor.c |    2 +-
 test/test-proximity |    4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/proximity/monitor.c b/proximity/monitor.c
index 76020ee..7bf95a1 100644
--- a/proximity/monitor.c
+++ b/proximity/monitor.c
@@ -49,7 +49,7 @@
 #include "monitor.h"
 #include "textfile.h"
 
-#define PROXIMITY_INTERFACE "org.bluez.Proximity"
+#define PROXIMITY_INTERFACE "org.bluez.ProximityMonitor"
 
 #define ALERT_LEVEL_CHR_UUID 0x2A06
 #define POWER_LEVEL_CHR_UUID 0x2A07
diff --git a/test/test-proximity b/test/test-proximity
index 289908e..130590c 100755
--- a/test/test-proximity
+++ b/test/test-proximity
@@ -53,11 +53,11 @@ if __name__ == "__main__":
 	device_path = adapter.FindDevice(options.address)
 
 	bus.add_signal_receiver(property_changed, bus_name="org.bluez",
-				dbus_interface="org.bluez.Proximity",
+				dbus_interface="org.bluez.ProximityMonitor",
 				signal_name="PropertyChanged")
 
 	proximity = dbus.Interface(bus.get_object("org.bluez",
-					device_path), "org.bluez.Proximity")
+					device_path), "org.bluez.ProximityMonitor")
 
 	print "Proximity SetProperty('%s', '%s')" % (args[0], args[1])
 	proximity.SetProperty(args[0], args[1])
-- 
1.7.5.4


             reply	other threads:[~2012-02-03 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 13:42 Anderson Lizardo [this message]
2012-02-09 12:59 ` [PATCH BlueZ] proximity: Fix Proximity API to match documentation Anderson Lizardo
2012-02-09 13:11 ` Johan Hedberg

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=1328276576-2996-1-git-send-email-anderson.lizardo@openbossa.org \
    --to=anderson.lizardo@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).