From: Jonathan Nieder <jrnieder@gmail.com>
To: stable@vger.kernel.org
Cc: Arend van Spriel <arend@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>,
Touko Korpela <touko.korpela@iki.fi>,
linux-wireless@vger.kernel.org
Subject: [3.2.y] Re: [PATCH 2/2] brcm80211: smac: only print block-ack timeout message at trace level
Date: Sat, 24 Nov 2012 15:14:38 -0800 [thread overview]
Message-ID: <20121124231438.GA26176@elie.Belkin> (raw)
In-Reply-To: <1330018703-2472-3-git-send-email-arend@broadcom.com>
Hi Ben,
Please consider
2b0a53d51b5f brcm80211: smac: only print block-ack timeout message
at trace level
for application to the 3.2.y tree.
It just lowers the priority of a distracting repeated message about a
normal condition:
ieee80211 phy0: AMPDU status: BA Timeout, seq 152, in_transit 0
See <http://bugs.debian.org/674430> for context.
The patch was applied upstream during the 3.3-rc7 cycle. Applying it
should make debugging other problems easier. Thoughts of all kinds
welcome, as always.
Regards,
Jonathan
next prev parent reply other threads:[~2012-11-24 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 17:38 [PATCH for 3.3 0/2] brcm80211: fix endless A-MPDU retries Arend van Spriel
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 ` Jonathan Nieder [this message]
2012-12-02 3:35 ` [3.2.y] " 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=20121124231438.GA26176@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=stable@vger.kernel.org \
--cc=touko.korpela@iki.fi \
/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).