From: Gustavo Padovan <gustavo@padovan.org>
To: linux-bluetooth@vger.kernel.org
Cc: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
Subject: [RFC v1 4/9] adapter: rename compare_discovery_sender
Date: Tue, 11 Jun 2013 01:03:26 +0100 [thread overview]
Message-ID: <1370909011-19315-4-git-send-email-gustavo@padovan.org> (raw)
In-Reply-To: <1370909011-19315-1-git-send-email-gustavo@padovan.org>
From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
The new name "compare_sender" is more generic and will be used for more
than one purpose.
---
src/adapter.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/adapter.c b/src/adapter.c
index 0277057..bb5737e 100644
--- a/src/adapter.c
+++ b/src/adapter.c
@@ -1478,7 +1478,7 @@ static void stop_discovery_complete(uint8_t status, uint16_t length,
}
}
-static int compare_discovery_sender(gconstpointer a, gconstpointer b)
+static int compare_sender(gconstpointer a, gconstpointer b)
{
const struct watch_client *client = a;
const char *sender = b;
@@ -1617,7 +1617,7 @@ static DBusMessage *start_discovery(DBusConnection *conn,
* already started a discovery then return an error.
*/
list = g_slist_find_custom(adapter->discovery_list, sender,
- compare_discovery_sender);
+ compare_sender);
if (list)
return btd_error_busy(msg);
@@ -1657,7 +1657,7 @@ static DBusMessage *stop_discovery(DBusConnection *conn,
return btd_error_not_ready(msg);
list = g_slist_find_custom(adapter->discovery_list, sender,
- compare_discovery_sender);
+ compare_sender);
if (!list)
return btd_error_failed(msg, "No discovery started");
--
1.8.1.4
next prev parent reply other threads:[~2013-06-11 0:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 0:03 [RFC v1 1/9] adapter: fix setting of discoverable timeout Gustavo Padovan
2013-06-11 0:03 ` [RFC v1 2/9] adapter: remove unused toggle_discoverable Gustavo Padovan
2013-06-11 0:03 ` [RFC v1 3/9] adapter: rename discovery_client to watch_client Gustavo Padovan
2013-06-11 0:03 ` Gustavo Padovan [this message]
2013-06-11 0:03 ` [RFC v1 5/9] doc: add RequestPairingSession() and ReleasePairingSession() Gustavo Padovan
2013-06-11 1:22 ` Marcel Holtmann
2013-06-11 10:00 ` Bastien Nocera
2013-06-11 10:07 ` Gustavo Padovan
2013-06-11 10:14 ` Bastien Nocera
2013-06-11 0:03 ` [RFC v1 6/9] adapter: " Gustavo Padovan
2013-06-11 0:03 ` [RFC v1 7/9] adapter: add Pairing property to report ongoing Pairing Session Gustavo Padovan
2013-06-11 0:03 ` [RFC v1 8/9] adapter: forbid properties to be set during " Gustavo Padovan
2013-06-11 0:03 ` [RFC v1 9/9] test: add pairing command to test-adapter Gustavo Padovan
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=1370909011-19315-4-git-send-email-gustavo@padovan.org \
--to=gustavo@padovan.org \
--cc=gustavo.padovan@collabora.co.uk \
--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).