From: "John W. Linville" <linville@tuxdriver.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: pull request: iwlwifi-2014-08-14
Date: Thu, 14 Aug 2014 14:21:26 -0400 [thread overview]
Message-ID: <20140814182126.GE4953@tuxdriver.com> (raw)
In-Reply-To: <CANUX_P0LJqMS40k=8jeie3q=nbXsA4qO39TL3G9gkp+cTshMCw@mail.gmail.com>
On Thu, Aug 14, 2014 at 11:12:30AM -0700, Emmanuel Grumbach wrote:
> Hi John,
>
> This is a pull request with one patch that fixes an issue faced by Linus.
>
> David Spinadel helped me debugging this and it appears that the
> firmware currently available doesn't support scheduled scan. So we
> disable that for now.
>
> I am sorry - but I am travelling right now and my connection to the
> only computer that has my PGP signature is awfully slow...
> Please pull. I'll try to sign a reply to this message as soon as I can.
>
> Thanks,
>
> The following changes since commit 2da2c5854ed759a64f8a9231a7f544b472c3aa6d:
>
> net: wireless: ipw2x00: ipw2200.c: Cleaning up missing
> null-terminate after strncpy call (2014-08-11 14:43:51 -0400)
>
> 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 77b2f2865956b7573f9b040db7a9f808b434acd1:
>
> iwlwifi: mvm: disable scheduled scan to prevent firmware crash
> (2014-08-14 19:47:41 +0300)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2014-08-14 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 18:12 pull request: iwlwifi-2014-08-14 Emmanuel Grumbach
2014-08-14 18:21 ` 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=20140814182126.GE4953@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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).