From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>, Felix Fietkau <nbd@nbd.name>
Cc: "A. Benz" <ash.benz@bk.ru>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: ath10k/QCA9980 - Issues introduced in wireless testing 2016-05
Date: Fri, 10 Jun 2016 11:20:53 +0200 [thread overview]
Message-ID: <1465550453.2308.0.camel@sipsolutions.net> (raw)
In-Reply-To: <CA+BoTQ=xWetiO9GK_staz=M=rAT4_tA5khedqn206mjyRHsmQg@mail.gmail.com> (sfid-20160610_111051_322091_FF8AB05C)
On Fri, 2016-06-10 at 11:10 +0200, Michal Kazior wrote:
>
> Hmm.. could it be related to ath10k not fulfilling (some) NAPI's
> locking requirements and thus ending up with, e.g. linked-list
> mayhem?
>
Shoudln't matter since ath10k doesn't actually use rx_napi()?
johannes
next prev parent reply other threads:[~2016-06-10 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 7:46 ath10k/QCA9980 - Issues introduced in wireless testing 2016-05 A. Benz
2016-06-10 8:50 ` Michal Kazior
2016-06-10 8:55 ` Felix Fietkau
2016-06-10 9:10 ` Michal Kazior
2016-06-10 9:20 ` Johannes Berg [this message]
2016-06-10 12:22 ` Kalle Valo
2016-06-10 12:52 ` Ben Greear
2016-06-10 12:57 ` Felix Fietkau
2016-06-10 13:16 ` Ben Greear
2016-07-15 11:49 ` Nagarajan, Ashok Raj
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=1465550453.2308.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ash.benz@bk.ru \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=nbd@nbd.name \
/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).