From: Felix Fietkau <nbd@openwrt.org>
To: linux-wireless@vger.kernel.org
Cc: linville@tuxdriver.com
Subject: Re: [PATCH 3.18 3/3] ath9k: do not access hardware on IRQs during reset
Date: Sat, 15 Nov 2014 23:46:44 +0100 [thread overview]
Message-ID: <5467D7D4.6090304@openwrt.org> (raw)
In-Reply-To: <1415900045-49093-3-git-send-email-nbd@openwrt.org>
On 2014-11-13 18:34, Felix Fietkau wrote:
> Instead of killing interrupts during reset when the first one happens,
> kill them before issuing the reset.
> This fixes an easy to reproduce crash with multiple cards sharing the
> same IRQ.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Felix Fietkau <nbd@openwrt.org>
Please disregard this series for now, it seems to be causing some issues
on a few SoC devices.
- Felix
prev parent reply other threads:[~2014-11-15 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 17:34 [PATCH 3.18 1/3] ath9k: prevent early IRQs from accessing hardware Felix Fietkau
2014-11-13 17:34 ` [PATCH 3.18 2/3] ath9k: set ATH_OP_INVALID before disabling hardware Felix Fietkau
2014-11-13 17:34 ` [PATCH 3.18 3/3] ath9k: do not access hardware on IRQs during reset Felix Fietkau
2014-11-15 22:46 ` 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=5467D7D4.6090304@openwrt.org \
--to=nbd@openwrt.org \
--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).