All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ilw@linux.intel.com" <ilw@linux.intel.com>
Subject: Re: pull request: iwlwifi 2014-02-23
Date: Mon, 24 Feb 2014 14:42:26 -0500	[thread overview]
Message-ID: <20140224194225.GC24810@tuxdriver.com> (raw)
In-Reply-To: <530A49C8.8060502@gmail.com>

On Sun, Feb 23, 2014 at 09:19:36PM +0200, Emmanuel Grumbach wrote:
> 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)

Pulling now...

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

      parent reply	other threads:[~2014-02-24 19:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23 19:19 pull request: iwlwifi 2014-02-23 Emmanuel Grumbach
2014-02-23 19:22 ` [PATCH] iwlwifi: dvm: clear IWL_STA_UCODE_INPROGRESS when assoc fails Emmanuel Grumbach
2014-02-24 19:42 ` 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=20140224194225.GC24810@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=egrumbach@gmail.com \
    --cc=ilw@linux.intel.com \
    --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.