Linux wireless drivers development
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-wireless@vger.kernel.org, Alan Piszcz <ap@solarrain.com>
Subject: Re: 3.0.0: carl9170: drivers/net/wireless/ath/carl9170/tx.c:351 carl9170_tx_status+0x431/0x440 [carl9170]()
Date: Tue, 6 Sep 2011 11:04:22 -0400	[thread overview]
Message-ID: <20110906110422.326f95c5@mj> (raw)
In-Reply-To: <alpine.DEB.2.02.1109051750010.23828@p34.internal.lan>

On Mon, 5 Sep 2011 17:53:06 -0400 (EDT)
Justin Piszcz <jpiszcz@lucidpixels.com> wrote:

> Hello,
> 
> Saw this on one of my Linux machines with a Linux (community
> supported USB stick):
> 
> [88927.073741] ------------[ cut here ]------------
> [88927.073762] WARNING: at drivers/net/wireless/ath/carl9170/tx.c:351

I'm dropping LKML from cc, no need to write there if there is a specialized
mailing list.

It looks like the bitmap code in carl9170 needs reviewing.  I spotted
one error immediately.  bitmap_zero() takes the number of bits, not the
number of long integers.

Chances are not very high that it would help in your case, but here's
the patch.  I hope to give carl9170 some good testing before submitting
that patch formally.

carl9170: fix bitmap initialization

From: Pavel Roskin <proski@gnu.org>

bitmap_zero() takes the number of bits, not the long integers used to
keep them.

Signed-off-by: Pavel Roskin <proski@gnu.org>
---

 drivers/net/wireless/ath/carl9170/main.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


diff --git a/drivers/net/wireless/ath/carl9170/main.c b/drivers/net/wireless/ath/carl9170/main.c
index af351ec..2f68747 100644
--- a/drivers/net/wireless/ath/carl9170/main.c
+++ b/drivers/net/wireless/ath/carl9170/main.c
@@ -1411,7 +1411,7 @@ static int carl9170_op_ampdu_action(struct ieee80211_hw *hw,
 		sta_info->stats[tid].req = false;
 
 		if (tid_info) {
-			bitmap_zero(tid_info->bitmap, CARL9170_BAW_SIZE);
+			bitmap_zero(tid_info->bitmap, CARL9170_BAW_BITS);
 			tid_info->state = CARL9170_TID_STATE_IDLE;
 		}
 		rcu_read_unlock();

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2011-09-06 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05 21:53 3.0.0: carl9170: drivers/net/wireless/ath/carl9170/tx.c:351 carl9170_tx_status+0x431/0x440 [carl9170]() Justin Piszcz
2011-09-06 15:04 ` Pavel Roskin [this message]
2011-09-06 18:39   ` Justin Piszcz

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=20110906110422.326f95c5@mj \
    --to=proski@gnu.org \
    --cc=ap@solarrain.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-wireless@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