From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Jake Edge <jake@lwn.net>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [RFT/RFC 0/4] iwlegacy: workaround for firmware frame tx rejection
Date: Sat, 25 May 2013 08:49:36 +0200 [thread overview]
Message-ID: <20130525064935.GA1599@redhat.com> (raw)
In-Reply-To: <20130524171846.54f3d0be@chukar.edge2.net>
On Fri, May 24, 2013 at 05:18:46PM -0600, Jake Edge wrote:
> On Thu, 23 May 2013 14:20:56 +0200 Stanislaw Gruszka wrote:
> > Jake, please test this set and check if it not cause association
> > problems you reported earlier this month.
>
> I won't be able to get to this for 10 days or so ... I just got to
> Japan, so the AP in question is thousands of miles east :)
No problem, it doesn't have to be fast. I plan to post patches to
-next (i.e. 3.11), since we have simpler workaround already applied.
Thanks
Stanislaw
next prev parent reply other threads:[~2013-05-25 6:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 12:20 [RFT/RFC 0/4] iwlegacy: workaround for firmware frame tx rejection Stanislaw Gruszka
2013-05-23 12:20 ` [RFT/RFC 1/4] iwlegacy: small refactoring of il_{stop,wake}_queue Stanislaw Gruszka
2013-05-23 12:20 ` [RFT/RFC 2/4] iwlegacy: add il_{stop,wake}_queues_by_reason functions Stanislaw Gruszka
2013-05-23 12:20 ` [RFT/RFC 3/4] iwlegacy: workaround for firmware frame tx rejection Stanislaw Gruszka
2013-05-23 12:21 ` [RFT/RFC 4/4] Revert "iwl4965: workaround connection regression on passive channel" Stanislaw Gruszka
2013-05-25 8:55 ` [RFT/RFC 5/4] iwlegacy: unblock queues on passive channel if any frame receive Stanislaw Gruszka
2013-05-24 20:26 ` [RFT/RFC 0/4] iwlegacy: workaround for firmware frame tx rejection Johannes Berg
2013-05-25 8:53 ` Stanislaw Gruszka
2013-05-24 23:18 ` Jake Edge
2013-05-25 6:49 ` Stanislaw Gruszka [this message]
2013-06-10 20:38 ` Jake Edge
2013-06-11 3:41 ` Jake Edge
2013-06-11 16:09 ` Stanislaw Gruszka
2013-06-11 19:17 ` Jake Edge
2013-06-12 14: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=20130525064935.GA1599@redhat.com \
--to=sgruszka@redhat.com \
--cc=jake@lwn.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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.