linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: David Miller <davem@davemloft.net>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: pull-request: wireless-drivers 2017-11-22
Date: Wed, 22 Nov 2017 17:27:22 +0200	[thread overview]
Message-ID: <87mv3ebag5.fsf@kamboji.qca.qualcomm.com> (raw)

Hi Dave,

here's the first pull request to net tree for 4.15. Please let me know
if there are any problems.

Kalle

The following changes since commit 32a72bbd5da2411eab591bf9bc2e39349106193a:

  net: vxge: Fix some indentation issues (2017-11-20 11:36:30 +0900)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git tags/wireless-drivers-for-davem-2017-11-22

for you to fetch changes up to ed59b7d53c95548d83d4e7e1bc5edafcdcad09c9:

  Merge ath-current from git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git (2017-11-21 11:52:18 +0200)

----------------------------------------------------------------
wireless-drivers fixes for 4.15

First set of fixes for 4.15. Most important here is the iwlwifi fix
for scan command firmware interface change.

ath10k

* fix CCMP-256, GCMP and GCMP-256 in raw mode, it was never working

wcn36xx

* fix device tree node search

iwlwifi

* fix a regression with firmware API change of scan cmd (introduced in
  firmware version 34)

* add a bunch of PCI IDs and fix configuration structs for A000 devices

* fix the exported firmware name strings for 9000 and A000 devices

----------------------------------------------------------------
Johan Hovold (1):
      wcn36xx: fix iris child-node lookup

Kalle Valo (2):
      Merge tag 'iwlwifi-for-kalle-2017-11-19' of git://git.kernel.org/.../iwlwifi/iwlwifi-fixes
      Merge ath-current from git://git.kernel.org/.../kvalo/ath.git

Luca Coelho (2):
      iwlwifi: mvm: support version 7 of the SCAN_REQ_UMAC FW command
      iwlwifi: fix PCI IDs and configuration mapping for 9000 series

Thomas Backlund (1):
      iwlwifi: fix firmware names for 9000 and A000 series hw

Vasanthakumar Thiagarajan (1):
      ath10k: fix data rx for CCMP-256, GCMP and GCMP-256 in raw mode

 drivers/net/wireless/ath/ath10k/htt_rx.c         |  51 ++++++---
 drivers/net/wireless/ath/wcn36xx/main.c          |   2 +-
 drivers/net/wireless/intel/iwlwifi/cfg/9000.c    |  73 +++++++++++--
 drivers/net/wireless/intel/iwlwifi/cfg/a000.c    |  10 +-
 drivers/net/wireless/intel/iwlwifi/fw/api/scan.h |  59 +++++++---
 drivers/net/wireless/intel/iwlwifi/fw/file.h     |   1 +
 drivers/net/wireless/intel/iwlwifi/iwl-config.h  |   5 +
 drivers/net/wireless/intel/iwlwifi/mvm/mvm.h     |   6 ++
 drivers/net/wireless/intel/iwlwifi/mvm/scan.c    |  86 +++++++++++----
 drivers/net/wireless/intel/iwlwifi/pcie/drv.c    | 132 ++++++++++++++++++-----
 10 files changed, 335 insertions(+), 90 deletions(-)

             reply	other threads:[~2017-11-22 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-22 15:27 Kalle Valo [this message]
2017-11-23 18:07 ` pull-request: wireless-drivers 2017-11-22 David Miller

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=87mv3ebag5.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@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 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).