Re: pull request: iwlwifi-2016-02-16

[Coelho, Luciano]

Hi Arend,

On Fri, 2016-03-18 at 20:52 +0100, Arend Van Spriel wrote:
> 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?

I don't remember exactly what was the scenario, but I think it was when
wpa_s had a single AP configure and failed to connect to it (and
blacklisted it).  Then it would try a couple of regular scans with
broadcast SSID then switch to sched scan.

I'll dig the bug up next week so I can tell you for sure.

--
Cheers,
Luca.N�r��yb�X��ǧv�^�)޺{.n�+{��*ޕ�,�{ay�ʇڙ�,j��f���h���z��w���
���j:+v���w�j�mzZ+�ݢj"��!�i

Re: pull request: iwlwifi-2016-02-16

[Kalle Valo]

"Grumbach, Emmanuel"  writes:

> This is a pull request for 4.5. Apart from my RF-Kill fix, the patches are
> really small. My RF-Kill patch needed to move code around to avoid adding
> a forward declaration and on the way there were a few very trivial code style
> fixes, that were needed to make checkpatch happy.
>
> Let me know if you have issues, thanks!
>
>
> The following changes since commit 69c7fda40921c125f6a827f6270ac6aa1baa:
>
>   iwlwifi: mvm: rs: fix TPC statistics handling (2016-01-26 16:03:35 +0200)
>
> are available in the git repository at:
>
>   https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git 
> tags/iwlwifi-for-kalle-2016-02-15

Pulled, thanks.

-- 
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

pull request: iwlwifi-2016-02-16

[Grumbach, Emmanuel]

Hi Kalle,

This is a pull request for 4.5. Apart from my RF-Kill fix, the patches are
really small. My RF-Kill patch needed to move code around to avoid adding
a forward declaration and on the way there were a few very trivial code style
fixes, that were needed to make checkpatch happy.

Let me know if you have issues, thanks!


The following changes since commit 69c7fda40921c125f6a827f6270ac6aa1baa:

  iwlwifi: mvm: rs: fix TPC statistics handling (2016-01-26 16:03:35 +0200)

are available in the git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git 
tags/iwlwifi-for-kalle-2016-02-15

for you to fetch changes up to 20aa99bbddae74bded68338f9ba200ccae02858b:

  iwlwifi: pcie: fix erroneous return value (2016-02-15 13:38:31 +0200)


These are a few fixes for the current cycle.
3 out of the 5 patches fix a bugzilla.

* fix a race that users reported when we try to load the firmware
  and the hardware rfkill interrupt triggers at the same time.
* 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.
* build system fix
* firmware name update for 8265
* typo fix in return value


Anton Protopopov (1):
  iwlwifi: pcie: fix erroneous return value

Emmanuel Grumbach (2):
  iwlwifi: dvm: remove a wrong dependency on m
  iwlwifi: pcie: fix RF-Kill vs. firmware load race

Luca Coelho (1):
  iwlwifi: mvm: don't allow sched scans without matches to be started

Oren Givon (1):
  iwlwifi: fix name of ucode loaded for 8265 series

 drivers/net/wireless/intel/iwlwifi/Kconfig |   1 -
 drivers/net/wireless/intel/iwlwifi/iwl-8000.c  |  42 --
 drivers/net/wireless/intel/iwlwifi/iwl-drv.c   |   6 +-
 drivers/net/wireless/intel/iwlwifi/mvm/scan.c  |   4 +
 drivers/net/wireless/intel/iwlwifi/pcie/internal.h |   9 ++
 drivers/net/wireless/intel/iwlwifi/pcie/rx.c   |   8 +-
 drivers/net/wireless/intel/iwlwifi/pcie/trans.c| 188 
--
 7 files changed, 164 insertions(+), 94 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html