Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Marcin Kraglak <marcin.kraglak@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] android/gatt: Fix incorrect event status
Date: Thu, 10 Apr 2014 10:54:34 +0200	[thread overview]
Message-ID: <11455563.3Ct9QDaxCl@uw000953> (raw)
In-Reply-To: <1397111398-18137-1-git-send-email-marcin.kraglak@tieto.com>

Hi Marcin,

On Thursday 10 of April 2014 08:29:58 Marcin Kraglak wrote:
> Return proper gatt_status in register_for_notification event.
> ---
>  android/gatt.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/android/gatt.c b/android/gatt.c
> index 15e788a..971e2dd 100644
> --- a/android/gatt.c
> +++ b/android/gatt.c
> @@ -2482,7 +2482,7 @@ static void handle_client_register_for_notification(const void *buf,
>  	status = HAL_STATUS_SUCCESS;
>  
>  failed:
> -	gatt_status  = status ? GATT_SUCCESS : GATT_FAILURE;
> +	gatt_status = status ? GATT_FAILURE : GATT_SUCCESS;
>  	send_register_for_notification_ev(conn_id, 1, gatt_status,
>  						&cmd->srvc_id, &cmd->char_id);
>  	ipc_send_rsp(hal_ipc, HAL_SERVICE_ID_GATT,
> @@ -2535,7 +2535,7 @@ static void handle_client_deregister_for_notification(const void *buf,
>  	status = HAL_STATUS_SUCCESS;
>  
>  failed:
> -	gatt_status  = status ? GATT_SUCCESS : GATT_FAILURE;
> +	gatt_status = status ? GATT_FAILURE : GATT_SUCCESS;
>  	send_register_for_notification_ev(conn_id, 0, gatt_status,
>  						&cmd->srvc_id, &cmd->char_id);
>  
> 

Patch applied. Thanks.

-- 
Best regards, 
Szymon Janc

      reply	other threads:[~2014-04-10  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10  6:29 [PATCH] android/gatt: Fix incorrect event status Marcin Kraglak
2014-04-10  8:54 ` Szymon Janc [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=11455563.3Ct9QDaxCl@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcin.kraglak@tieto.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