linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: iwlwifi-fixes 2013-03-28
Date: Thu, 28 Mar 2013 16:35:49 +0100	[thread overview]
Message-ID: <1364484949.10397.7.camel@jlt4.sipsolutions.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]

Hi John,

I know you just pulled my other iwlwifi-fixes request ... but in the
meantime I debugged with Alex Romosan, you probably saw the thread, and
thus have another fix and I wanted to send it to you.

The only fix here is to the passive-no-RX firmware regulatory
enforcement driver support code to not drop auth frames in quick
succession, leading to not being able to connect to APs on passive
channels in certain circumstances.

Let me know if there's any issue. Thanks,
johannes


The following changes since commit 2d5d50ee596361566f7f84300117cba7d7672bc5:

  iwlwifi: dvm: don't send HCMD in restart flow (2013-03-20 12:10:57 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git for-john

for you to fetch changes up to b8730b403aee94db4631bfefb546a6ce8c287dc2:

  iwlwifi: dvm: fix the passive-no-RX workaround (2013-03-28 16:31:26 +0100)

----------------------------------------------------------------
Johannes Berg (1):
      iwlwifi: dvm: fix the passive-no-RX workaround

 drivers/net/wireless/iwlwifi/dvm/rxon.c | 18 ++++++++----------
 drivers/net/wireless/iwlwifi/dvm/tx.c   |  2 +-
 2 files changed, 9 insertions(+), 11 deletions(-)


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

             reply	other threads:[~2013-03-28 15:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 15:35 Johannes Berg [this message]
2013-04-01 19:10 ` pull-request: iwlwifi-fixes 2013-03-28 John W. Linville

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=1364484949.10397.7.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --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).