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,
	Johannes Berg <johannes@sipsolutions.net>
Subject: pull-request: wireless-drivers 2019-08-21
Date: Wed, 21 Aug 2019 09:07:30 +0300	[thread overview]
Message-ID: <87zhk359wd.fsf@kamboji.qca.qualcomm.com> (raw)

Hi Dave,

here's a pull request to net for 5.3, more info below. I will be offline
the next week, but Johannes should be able to help if there are any
issues.

Kalle


The following changes since commit d1abaeb3be7b5fa6d7a1fbbd2e14e3310005c4c1:

  Linux 5.3-rc5 (2019-08-18 14:31:08 -0700)

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-2019-08-21

for you to fetch changes up to 5a8c31aa63578cb0ff390a57537f1cb4b312a1ed:

  iwlwifi: pcie: fix recognition of QuZ devices (2019-08-20 17:00:42 +0300)

----------------------------------------------------------------
wireless-drivers fixes for 5.3

Third set of fixes for 5.3, and most likely the last one. The rt2x00
regression has been reported multiple times, others are of lower
priority.

mt76

* fix hang on resume on certain machines

rt2x00

* fix AP mode regression related to encryption

iwlwifi

* avoid unnecessary error messages due to multicast frames when not
  associated

* fix configuration for ax201 devices

* fix recognition of QuZ devices

----------------------------------------------------------------
Emmanuel Grumbach (1):
      iwlwifi: pcie: fix the byte count table format for 22560 devices

Ilan Peer (1):
      iwlwifi: mvm: Allow multicast data frames only when associated

Luca Coelho (2):
      iwlwifi: pcie: don't switch FW to qnj when ax201 is detected
      iwlwifi: pcie: fix recognition of QuZ devices

Stanislaw Gruszka (2):
      mt76: mt76x0u: do not reset radio on resume
      rt2x00: clear IV's on start to fix AP mode regression

 drivers/net/wireless/intel/iwlwifi/mvm/mac-ctxt.c | 33 ++++++++++++++++++++---
 drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c | 10 +++++++
 drivers/net/wireless/intel/iwlwifi/pcie/drv.c     | 17 ++++++++++++
 drivers/net/wireless/intel/iwlwifi/pcie/trans.c   |  1 +
 drivers/net/wireless/intel/iwlwifi/pcie/tx-gen2.c | 20 +++++++++-----
 drivers/net/wireless/mediatek/mt76/mt76x0/usb.c   |  8 +++---
 drivers/net/wireless/ralink/rt2x00/rt2800lib.c    |  9 +++++++
 drivers/net/wireless/ralink/rt2x00/rt2x00.h       |  1 +
 drivers/net/wireless/ralink/rt2x00/rt2x00dev.c    | 13 +++++----
 9 files changed, 93 insertions(+), 19 deletions(-)

             reply	other threads:[~2019-08-21  6:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21  6:07 Kalle Valo [this message]
2019-08-22 23:12 ` pull-request: wireless-drivers 2019-08-21 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=87zhk359wd.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=davem@davemloft.net \
    --cc=johannes@sipsolutions.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).