linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, "Arend van Spriel" <arend@broadcom.com>
Subject: [PATCH for 3.3 0/2] brcm80211: fix endless A-MPDU retries
Date: Thu, 23 Feb 2012 18:38:21 +0100	[thread overview]
Message-ID: <1330018703-2472-1-git-send-email-arend@broadcom.com> (raw)

Hi John,

The first patch has already been taken in wireless-next repo. However,
as people see the issue with 3.2 and 3.3 kernels it should go to wireless
repository as well.

Fix endless retries that became more obvious upon implementing the
mac80211 flush callback and more so after adding the WARN_ON_ONCE
by Stanislaw Gruszka (https://bugzilla.kernel.org/show_bug.cgi?id=42576).

These second patch removes error print to limit the mess printed in the
log when an A-MPDU transmission times out on the block-ack.

Arend van Spriel (2):
  brcm80211: smac: fix endless retry of A-MPDU transmissions
  brcm80211: smac: only print block-ack timeout message at trace level

 drivers/net/wireless/brcm80211/brcmsmac/ampdu.c |   12 ++++--------
 1 files changed, 4 insertions(+), 8 deletions(-)

-- 
1.7.5.4



             reply	other threads:[~2012-02-23 17:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 17:38 Arend van Spriel [this message]
2012-02-23 17:38 ` [PATCH 1/2] brcm80211: smac: fix endless retry of A-MPDU transmissions Arend van Spriel
2012-05-16 22:28   ` [PATCH 3.2.y, 3.3.y] " Jonathan Nieder
2012-05-17  0:05     ` Ben Hutchings
2012-05-18 19:58     ` Greg KH
2012-05-18 20:51       ` Jonathan Nieder
2012-05-19  8:49         ` Arend van Spriel
2012-05-19 16:53           ` Jonathan Nieder
2012-02-23 17:38 ` [PATCH 2/2] brcm80211: smac: only print block-ack timeout message at trace level Arend van Spriel
2012-11-24 23:14   ` [3.2.y] " Jonathan Nieder
2012-12-02  3:35     ` Ben Hutchings

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=1330018703-2472-1-git-send-email-arend@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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;
as well as URLs for NNTP newsgroup(s).