From: Michael Brudevold <puffy.taco@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Michael Brudevold <michael.brudevold@veranexsolutions.com>
Subject: [PATCH v2 3/3] neard: Update D-Bus path and interface
Date: Fri, 10 Jun 2022 17:11:24 -0500 [thread overview]
Message-ID: <20220610221124.18591-4-puffy.taco@gmail.com> (raw)
In-Reply-To: <20220610221124.18591-1-puffy.taco@gmail.com>
From: Michael Brudevold <michael.brudevold@veranexsolutions.com>
neard has been carrying legacy interfaces since 2013
---
plugins/neard.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/plugins/neard.c b/plugins/neard.c
index e03f981e0..77a4630da 100644
--- a/plugins/neard.c
+++ b/plugins/neard.c
@@ -33,8 +33,8 @@
#include "src/shared/util.h"
#define NEARD_NAME "org.neard"
-#define NEARD_PATH "/"
-#define NEARD_MANAGER_INTERFACE "org.neard.Manager"
+#define NEARD_PATH "/org/neard"
+#define NEARD_MANAGER_INTERFACE "org.neard.AgentManager"
#define AGENT_INTERFACE "org.neard.HandoverAgent"
#define AGENT_PATH "/org/bluez/neard_handover_agent"
#define AGENT_CARRIER_TYPE "bluetooth"
--
2.25.1
prev parent reply other threads:[~2022-06-10 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 22:11 [PATCH v2 0/3] LE OOB pairing support Michael Brudevold
2022-06-10 22:11 ` [PATCH v2 1/3] eir: parse data types for LE OOB pairing Michael Brudevold
2022-06-11 0:37 ` LE OOB pairing support bluez.test.bot
2022-06-11 20:27 ` [PATCH v2 1/3] eir: parse data types for LE OOB pairing Luiz Augusto von Dentz
2022-06-13 21:42 ` Mike Brudevold
2022-06-13 21:55 ` Luiz Augusto von Dentz
2022-06-13 22:28 ` Mike Brudevold
2022-06-21 18:57 ` Luiz Augusto von Dentz
2022-06-21 19:50 ` Mike Brudevold
2022-06-10 22:11 ` [PATCH v2 2/3] Accept LE formatted EIR data with neard plugin Michael Brudevold
2022-06-10 22:11 ` Michael Brudevold [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=20220610221124.18591-4-puffy.taco@gmail.com \
--to=puffy.taco@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=michael.brudevold@veranexsolutions.com \
/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).