From: Marcel Holtmann <marcel@holtmann.org>
To: "Weng, Wending" <WWeng@rheinmetall.ca>
Cc: "'linux-bluetooth@vger.kernel.org'" <linux-bluetooth@vger.kernel.org>
Subject: Re: patch for hci_bcsp.c(2.6.31.-rc1)
Date: Sat, 22 Aug 2009 13:05:38 -0700 [thread overview]
Message-ID: <1250971538.2950.26.camel@localhost.localdomain> (raw)
In-Reply-To: <54B31811B83D744D90BF0289EB447D460C1A5044@MAIL-MB1.oerlikon.ca>
Hi Wending,
> From 69596948eb2172080bb950d99dc90678ead08305 Mon Sep 17 00:00:00 2001
> From: root <root@SBC_PC_3.localdomain>
> Date: Wed, 19 Aug 2009 08:59:56 -0400
> Subject: [PATCH] The routine bcsp_pkt_cull doesn't ack the packets properly
> if multiple packets are queued. The counter i must increase before
> doing comparison.
>
> Signed-off-by: Wending Weng <wweng@rheinmetall.ca>
>
> ---
> drivers/bluetooth/hci_bcsp.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/bluetooth/hci_bcsp.c b/drivers/bluetooth/hci_bcsp.c
> index 894b2cb..cd30f39 100644
> --- a/drivers/bluetooth/hci_bcsp.c
> +++ b/drivers/bluetooth/hci_bcsp.c
> @@ -373,7 +373,7 @@ static void bcsp_pkt_cull(struct bcsp_struct *bcsp)
>
> i = 0;
> skb_queue_walk_safe(&bcsp->unack, skb, tmp) {
> - if (i++ >= pkts_to_be_removed)
> + if (++i >= pkts_to_be_removed)
> break;
wouldn't be if (i++ > pkts_to_be_removed) the better way to test this?
Regards
Marcel
next prev parent reply other threads:[~2009-08-22 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 13:19 patch for hci_bcsp.c(2.6.31.-rc1) Weng, Wending
2009-08-22 20:05 ` Marcel Holtmann [this message]
2009-08-24 14:03 ` Weng, Wending
2009-08-24 17:19 ` Marcel Holtmann
2009-08-24 18:33 ` Weng, Wending
2009-08-24 18:37 ` Marcel Holtmann
2009-08-24 20:19 ` patch for hci_bcsp.c(bluetooth-testing) Weng, Wending
2009-08-24 20:34 ` Marcel Holtmann
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=1250971538.2950.26.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=WWeng@rheinmetall.ca \
--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