From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [RFC/RFT] ath9k_htc: avoid scheduling while atomic on sta_rc_update
Date: Sun, 02 Feb 2014 10:02:15 +0100 [thread overview]
Message-ID: <52EE0997.1060402@rempel-privat.de> (raw)
In-Reply-To: <20140131193850.GC7648@redhat.com>
Am 31.01.2014 20:38, schrieb Stanislaw Gruszka:
> On Fri, Jan 31, 2014 at 07:24:05PM +0100, Oleksij Rempel wrote:
>> I have different HW. How can trigger sta_rc_update?
>
> Below patch should trigger it when any management frame is received
> from know sta and print information about it.
It seems to work,
a least it didn't crashed. I was able to trigger it only in IBSS mode.
--
Regards,
Oleksij
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 278 bytes
Desc: OpenPGP digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140202/6865ec30/attachment.pgp
WARNING: multiple messages have this Message-ID (diff)
From: Oleksij Rempel <linux@rempel-privat.de>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: ath9k-devel@venema.h4ckr.net, linux-wireless@vger.kernel.org
Subject: Re: [RFC/RFT] ath9k_htc: avoid scheduling while atomic on sta_rc_update
Date: Sun, 02 Feb 2014 10:02:15 +0100 [thread overview]
Message-ID: <52EE0997.1060402@rempel-privat.de> (raw)
In-Reply-To: <20140131193850.GC7648@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
Am 31.01.2014 20:38, schrieb Stanislaw Gruszka:
> On Fri, Jan 31, 2014 at 07:24:05PM +0100, Oleksij Rempel wrote:
>> I have different HW. How can trigger sta_rc_update?
>
> Below patch should trigger it when any management frame is received
> from know sta and print information about it.
It seems to work,
a least it didn't crashed. I was able to trigger it only in IBSS mode.
--
Regards,
Oleksij
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 278 bytes --]
next prev parent reply other threads:[~2014-02-02 9:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 13:37 [ath9k-devel] [RFC/RFT] ath9k_htc: avoid scheduling while atomic on sta_rc_update Stanislaw Gruszka
2014-01-31 13:37 ` Stanislaw Gruszka
2014-01-31 18:24 ` [ath9k-devel] " Oleksij Rempel
2014-01-31 18:24 ` Oleksij Rempel
2014-01-31 19:38 ` [ath9k-devel] " Stanislaw Gruszka
2014-01-31 19:38 ` Stanislaw Gruszka
2014-02-02 9:02 ` Oleksij Rempel [this message]
2014-02-02 9:02 ` Oleksij Rempel
2014-02-03 10:39 ` [ath9k-devel] " Stanislaw Gruszka
2014-02-03 10:39 ` Stanislaw Gruszka
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=52EE0997.1060402@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath9k-devel@lists.ath9k.org \
/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.