Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Ravi kumar Veeramally <ravikumar.veeramally@linux.intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 5/6] android/health: Notify application registration status
Date: Mon, 16 Jun 2014 10:59:33 +0200	[thread overview]
Message-ID: <7545894.rj9sN0mCY5@uw000953> (raw)
In-Reply-To: <1402578618-31484-6-git-send-email-ravikumar.veeramally@linux.intel.com>

Hi Ravi,

On Thursday 12 of June 2014 16:10:17 Ravi kumar Veeramally wrote:
> ---
>  android/health.c | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 
> diff --git a/android/health.c b/android/health.c
> index 45255df..687dfee 100644
> --- a/android/health.c
> +++ b/android/health.c
> @@ -105,6 +105,19 @@ static void free_health_app(void *data)
>  	free(app);
>  }
>  
> +static void send_app_reg_notify(struct health_app *app, uint8_t state)
> +{
> +	struct hal_ev_health_app_reg_state ev;
> +
> +	DBG("");
> +
> +	ev.id = app->id;
> +	ev.state = state;
> +
> +	ipc_send_notif(hal_ipc, HAL_SERVICE_ID_HEALTH,
> +				HAL_EV_HEALTH_APP_REG_STATE, sizeof(ev), &ev);
> +}
> +
>  static bool mdep_by_mdep_role(const void *data, const void *user_data)
>  {
>  	const struct mdep_cfg *mdep = data;
> @@ -660,6 +673,7 @@ static void bt_health_mdep_cfg_data(const void *buf, uint16_t len)
>  	}
>  
>  	status = HAL_STATUS_SUCCESS;
> +	send_app_reg_notify(app, HAL_HEALTH_APP_REG_SUCCESS);
>  
>  fail:
>  	if (status != HAL_STATUS_SUCCESS) {
> @@ -686,12 +700,15 @@ static void bt_health_unregister_app(const void *buf, uint16_t len)
>  		return;
>  	}
>  
> +	send_app_reg_notify(app, HAL_HEALTH_APP_DEREG_SUCCESS);
> +
>  	if (record_id > 0) {
>  		bt_adapter_remove_record(record_id);
>  		record_id = 0;
>  	}
>  
>  	free_health_app(app);
> +

Move this to proper patch (ie. one that added free_health_app call).
This makes bisecting easier.

>  	ipc_send_rsp(hal_ipc, HAL_SERVICE_ID_HEALTH,
>  				HAL_OP_HEALTH_UNREG_APP, HAL_STATUS_SUCCESS);
>  }
> 

-- 
Best regards, 
Szymon Janc

  reply	other threads:[~2014-06-16  8:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 13:10 [PATCH 0/6] HDP initial implementaion Ravi kumar Veeramally
2014-06-12 13:10 ` [PATCH 1/6] android/hal-health: Add channel state event handler Ravi kumar Veeramally
2014-06-16  7:25   ` Szymon Janc
2014-06-12 13:10 ` [PATCH 2/6] android/health: Cache health application data on app register call Ravi kumar Veeramally
2014-06-16  8:23   ` Szymon Janc
2014-06-16  9:22     ` Ravi kumar Veeramally
2014-06-16 12:02     ` Ravi kumar Veeramally
2014-06-12 13:10 ` [PATCH 3/6] android/health: Perform clean up on app unregister call Ravi kumar Veeramally
2014-06-12 13:10 ` [PATCH 4/6] android/health: Add HDP SDP record Ravi kumar Veeramally
2014-06-16  8:57   ` Szymon Janc
2014-06-16  9:18     ` Ravi kumar Veeramally
2014-06-16  9:26       ` Szymon Janc
2014-06-12 13:10 ` [PATCH 5/6] android/health: Notify application registration status Ravi kumar Veeramally
2014-06-16  8:59   ` Szymon Janc [this message]
2014-06-16  9:12     ` Ravi kumar Veeramally
2014-06-12 13:10 ` [PATCH 6/6] profile/health: Free sdp list after adding it to record Ravi kumar Veeramally

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=7545894.rj9sN0mCY5@uw000953 \
    --to=szymon.janc@tieto.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