From: Arend Van Spriel <arend.vanspriel@broadcom.com>
To: "Coelho, Luciano" <luciano.coelho@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Subject: Re: pull request: iwlwifi-2016-02-16
Date: Fri, 18 Mar 2016 20:52:35 +0100 [thread overview]
Message-ID: <56EC5C83.6070708@broadcom.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB32EA13D1A@hasmsx107.ger.corp.intel.com>
On 15-2-2016 12:57, Grumbach, Emmanuel wrote:
> * Luca fixes a very visible bug in scheduled scan: our firmware
> doesn't support scheduled scan with no profile configured and
> the supplicant sometimes requests such scheduled scans.
Hi Luca,
I have seen this happening as well, but did not find the exact scenario
in which supplicant does this. Would you happen to know?
Regards,
Arend
next prev parent reply other threads:[~2016-03-18 19:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 11:57 pull request: iwlwifi-2016-02-16 Grumbach, Emmanuel
2016-02-15 11:59 ` [PATCH 1/5] iwlwifi: fix name of ucode loaded for 8265 series Emmanuel Grumbach
2016-02-15 11:59 ` [PATCH 2/5] iwlwifi: dvm: remove a wrong dependency on m Emmanuel Grumbach
2016-02-15 11:59 ` [PATCH 3/5] iwlwifi: mvm: don't allow sched scans without matches to be started Emmanuel Grumbach
2016-02-15 11:59 ` [PATCH 4/5] iwlwifi: pcie: fix RF-Kill vs. firmware load race Emmanuel Grumbach
2016-02-15 11:59 ` [PATCH 5/5] iwlwifi: pcie: fix erroneous return value Emmanuel Grumbach
2016-02-16 16:02 ` pull request: iwlwifi-2016-02-16 Kalle Valo
2016-03-18 19:52 ` Arend Van Spriel [this message]
2016-03-18 20:03 ` Coelho, Luciano
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=56EC5C83.6070708@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.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).