From: Felix Fietkau <nbd@openwrt.org>
To: "Luis R. Rodriguez" <mcgrof@bombadil.infradead.org>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
mcgrof@qca.qualcomm.com
Subject: Re: [PATCH 3.9] ath9k: limit tx path hang check to normal data queues
Date: Fri, 15 Mar 2013 23:21:52 +0100 [thread overview]
Message-ID: <51439F00.9050001@openwrt.org> (raw)
In-Reply-To: <20130315183457.GB2676@bombadil.infradead.org>
On 2013-03-15 7:34 PM, Luis R. Rodriguez wrote:
> On Fri, Mar 15, 2013 at 04:18:44PM +0100, Felix Fietkau wrote:
>> The beacon and multicast-buffer queues are managed by the beacon
>> tasklet, and the generic tx path hang check does not help in any way
>> here. Running it on those queues anyway can introduce some race
>> conditions leading to unnecessary chip resets.
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
>
> This applies to v3.8 as well, do you want it there as well?
Yes
prev parent reply other threads:[~2013-03-15 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 15:18 [PATCH 3.9] ath9k: limit tx path hang check to normal data queues Felix Fietkau
2013-03-15 18:34 ` Luis R. Rodriguez
2013-03-15 22:21 ` Felix Fietkau [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=51439F00.9050001@openwrt.org \
--to=nbd@openwrt.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@bombadil.infradead.org \
--cc=mcgrof@qca.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.