From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH 08/11] android/health: Refactor setting mcl callbacks to function
Date: Tue, 24 Jun 2014 15:11:59 +0300 [thread overview]
Message-ID: <1403611922-26901-8-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1403611922-26901-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
Function will be used in other places as well.
---
android/health.c | 21 +++++++++++++--------
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/android/health.c b/android/health.c
index a9287f6..c4df17a 100644
--- a/android/health.c
+++ b/android/health.c
@@ -1252,6 +1252,18 @@ static int get_mdep(struct health_channel *channel)
get_mdep_cb, channel, NULL, 0);
}
+static bool set_mcl_cb(struct mcap_mcl *mcl, gpointer user_data, GError **err)
+{
+ return mcap_mcl_set_cb(mcl, user_data, err,
+ MCAP_MDL_CB_CONNECTED, mcap_mdl_connected_cb,
+ MCAP_MDL_CB_CLOSED, mcap_mdl_closed_cb,
+ MCAP_MDL_CB_DELETED, mcap_mdl_deleted_cb,
+ MCAP_MDL_CB_ABORTED, mcap_mdl_aborted_cb,
+ MCAP_MDL_CB_REMOTE_CONN_REQ, mcap_mdl_conn_req_cb,
+ MCAP_MDL_CB_REMOTE_RECONN_REQ, mcap_mdl_reconn_req_cb,
+ MCAP_MDL_CB_INVALID);
+}
+
static void create_mcl_cb(struct mcap_mcl *mcl, GError *err, gpointer data)
{
struct health_channel *channel = data;
@@ -1271,14 +1283,7 @@ static void create_mcl_cb(struct mcap_mcl *mcl, GError *err, gpointer data)
channel->dev->mcl_conn = true;
info("MCL connected");
- ret = mcap_mcl_set_cb(channel->dev->mcl, channel, &gerr,
- MCAP_MDL_CB_CONNECTED, mcap_mdl_connected_cb,
- MCAP_MDL_CB_CLOSED, mcap_mdl_closed_cb,
- MCAP_MDL_CB_DELETED, mcap_mdl_deleted_cb,
- MCAP_MDL_CB_ABORTED, mcap_mdl_aborted_cb,
- MCAP_MDL_CB_REMOTE_CONN_REQ, mcap_mdl_conn_req_cb,
- MCAP_MDL_CB_REMOTE_RECONN_REQ, mcap_mdl_reconn_req_cb,
- MCAP_MDL_CB_INVALID);
+ ret = set_mcl_cb(channel->dev->mcl, channel->dev, &gerr);
if (!ret) {
error("health: error setting mdl callbacks on mcl");
g_error_free(gerr);
--
1.8.3.2
next prev parent reply other threads:[~2014-06-24 12:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 12:11 [PATCH 01/11] android/hal-health: trivial: Correct coding style Andrei Emeltchenko
2014-06-24 12:11 ` [PATCH 02/11] android/health: Remove unneeded check Andrei Emeltchenko
2014-06-24 12:11 ` [PATCH 03/11] android/health: Fix possible overflow Andrei Emeltchenko
2014-06-24 12:11 ` [PATCH 04/11] android/health: Fix missing error check Andrei Emeltchenko
2014-06-24 12:11 ` [PATCH 05/11] android/health: trivial: Remove empty line Andrei Emeltchenko
2014-06-24 12:11 ` [PATCH 06/11] android/health: Remove extra check Andrei Emeltchenko
2014-06-24 12:11 ` [PATCH 07/11] android/health: trivial: Fix missing space Andrei Emeltchenko
2014-06-24 12:11 ` Andrei Emeltchenko [this message]
2014-06-24 12:12 ` [PATCH 09/11] android/health: Add actual error message to error print Andrei Emeltchenko
2014-06-24 12:12 ` [PATCH 10/11] android/health: Refactor create_device Andrei Emeltchenko
2014-06-24 12:12 ` [PATCH 11/11] android/health: Add setting mcl callbacks for incoming connection Andrei Emeltchenko
2014-06-25 15:30 ` [PATCH 01/11] android/hal-health: trivial: Correct coding style Szymon Janc
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=1403611922-26901-8-git-send-email-Andrei.Emeltchenko.news@gmail.com \
--to=andrei.emeltchenko.news@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