All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: iwlwifi-fixes 2013-03-28
Date: Mon, 1 Apr 2013 15:10:06 -0400	[thread overview]
Message-ID: <20130401191006.GA3526@tuxdriver.com> (raw)
In-Reply-To: <1364484949.10397.7.camel@jlt4.sipsolutions.net>

On Thu, Mar 28, 2013 at 04:35:49PM +0100, Johannes Berg wrote:
> 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)

Pulling now...

-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2013-04-01 19:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28 15:35 pull-request: iwlwifi-fixes 2013-03-28 Johannes Berg
2013-04-01 19:10 ` John W. Linville [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=20130401191006.GA3526@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --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.