From: Emmanuel Grumbach <egrumbach@gmail.com>
To: John Linville <linville@tuxdriver.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>
Subject: pull request: iwlwifi 2014-02-23
Date: Sun, 23 Feb 2014 21:19:36 +0200 [thread overview]
Message-ID: <530A49C8.8060502@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
Hi John,
One single patch for this pull request intended for 3.14.
This should fix an issue raised in iwldvm when we have lots of association failures.
There is a bugzilla for this bug - it hasn't been validated by the user, but I hope it will do the trick.
I hope I fixed my line wrapping issue this time. Let me know if you are still unhappy with the current format.
Thanks!
The following changes since commit 205e2210daa975d92ace485a65a31ccc4077fe1a:
iwlwifi: disable TX AMPDU by default for iwldvm (2014-02-13 15:24:35 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git master
for you to fetch changes up to ec6f678c74dbdb06a6a775bbb00f1d26c17c404b:
iwlwifi: dvm: clear IWL_STA_UCODE_INPROGRESS when assoc fails (2014-02-20 19:16:27 +0200)
----------------------------------------------------------------
Emmanuel Grumbach (1):
iwlwifi: dvm: clear IWL_STA_UCODE_INPROGRESS when assoc fails
drivers/net/wireless/iwlwifi/dvm/sta.c | 1 +
1 file changed, 1 insertion(+)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-02-23 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 19:19 Emmanuel Grumbach [this message]
2014-02-23 19:22 ` [PATCH] iwlwifi: dvm: clear IWL_STA_UCODE_INPROGRESS when assoc fails Emmanuel Grumbach
2014-02-24 19:42 ` pull request: iwlwifi 2014-02-23 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=530A49C8.8060502@gmail.com \
--to=egrumbach@gmail.com \
--cc=ilw@linux.intel.com \
--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).