From: Andrei Emeltchenko <andrei.emeltchenko.news@gmail.com>
To: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [RFC 5/5] android/health: Implement destroy_channel call
Date: Fri, 27 Jun 2014 17:13:02 +0300 [thread overview]
Message-ID: <20140627141224.GB21456@aemeltch-MOBL1> (raw)
In-Reply-To: <1403818246-20205-6-git-send-email-ravikumar.veeramally@linux.intel.com>
On Fri, Jun 27, 2014 at 12:30:46AM +0300, Ravi kumar Veeramally wrote:
> Delete MDL channel with MDL_DELETE_REQ.
> ---
> android/health.c | 25 +++++++++++++++++++++++--
> 1 file changed, 23 insertions(+), 2 deletions(-)
>
> diff --git a/android/health.c b/android/health.c
> index db3ae9c..e464f78 100644
> --- a/android/health.c
> +++ b/android/health.c
> @@ -1637,19 +1637,40 @@ fail:
> HAL_OP_HEALTH_CONNECT_CHANNEL, HAL_STATUS_FAILED);
> }
>
> +static void channel_delete_cb(GError *gerr, gpointer data)
> +{
> + struct health_channel *channel = data;
> +
> + DBG("");
> +
> + if (!gerr) {
> + error("health: channel delete failed %s", gerr->message);
I think this one may not work. I have sent a patch for this issue.
Best regards
Andrei Emeltchenko
next prev parent reply other threads:[~2014-06-27 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 21:30 [RFC 0/5] Implement MDL disconnect and reconnect Ravi kumar Veeramally
2014-06-26 21:30 ` [RFC 1/5] android/client/health: Introduce close_channel API Ravi kumar Veeramally
2014-06-26 21:30 ` [RFC 2/5] android/health: Implement mdl_closed_cb callback Ravi kumar Veeramally
2014-06-26 21:30 ` [RFC 3/5] android/health: Fix deleting channels queue Ravi kumar Veeramally
2014-06-26 21:30 ` [RFC 4/5] android/health: Implement mdl reconnect Ravi kumar Veeramally
2014-06-26 21:30 ` [RFC 5/5] android/health: Implement destroy_channel call Ravi kumar Veeramally
2014-06-27 14:13 ` Andrei Emeltchenko [this message]
2014-06-27 13:32 ` [RFC 0/5] Implement MDL disconnect and reconnect 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=20140627141224.GB21456@aemeltch-MOBL1 \
--to=andrei.emeltchenko.news@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravikumar.veeramally@linux.intel.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