Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Andrzej Kaczmarek <andrzej.kaczmarek@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/6] android/gatt: Remove redundant code
Date: Fri, 18 Apr 2014 15:25:37 +0200	[thread overview]
Message-ID: <1926493.D67Z9kgO2k@uw000953> (raw)
In-Reply-To: <1397781624-23817-1-git-send-email-andrzej.kaczmarek@tieto.com>

Hi Andrzej,

On Friday 18 of April 2014 02:40:19 Andrzej Kaczmarek wrote:
> cache_all_srvc_chars is called only with empty queue so it's redundant
> to handle this condition again inside function.
> ---
>  android/gatt.c | 4 ----
>  1 file changed, 4 deletions(-)
> 
> diff --git a/android/gatt.c b/android/gatt.c
> index e339789..59bcd23 100644
> --- a/android/gatt.c
> +++ b/android/gatt.c
> @@ -1739,10 +1739,6 @@ static void cache_all_srvc_chars(GSList *characteristics, struct queue *q)
>  	uint16_t inst_id = 0;
>  	bt_uuid_t uuid;
>  
> -	/* Refresh characteristics cache if already exist */
> -	if (!queue_isempty(q))
> -		queue_remove_all(q, NULL, NULL, destroy_characteristic);
> -
>  	for (; characteristics; characteristics = characteristics->next) {
>  		struct characteristic *ch;
>  
> 

All patches applied, thanks.

-- 
Best regards, 
Szymon Janc

      parent reply	other threads:[~2014-04-18 13:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18  0:40 [PATCH 1/6] android/gatt: Remove redundant code Andrzej Kaczmarek
2014-04-18  0:40 ` [PATCH 2/6] android/gatt: Cache end handle for characteristics Andrzej Kaczmarek
2014-04-18  0:40 ` [PATCH 3/6] android/gatt: Simplify discover_char_cb Andrzej Kaczmarek
2014-04-18  0:40 ` [PATCH 4/6] android/gatt: Use cached handle for descriptors discovery Andrzej Kaczmarek
2014-04-18  0:40 ` [PATCH 5/6] android/gatt: Simplify descriptor discovery structs Andrzej Kaczmarek
2014-04-18  0:40 ` [PATCH 6/6] android/gatt: Fix descriptors discovery Andrzej Kaczmarek
2014-04-18 13:25 ` 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=1926493.D67Z9kgO2k@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=andrzej.kaczmarek@tieto.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