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 2018-12-19
Date: Wed, 19 Dec 2018 16:34:02 +0200 [thread overview]
Message-ID: <87bm5hvb51.fsf@kamboji.qca.qualcomm.com> (raw)
Hi Dave,
this a pull request to net tree for 4.20, more info below.
Really sorry for sending a late request like this but I have been busy
with other stuff and this just got delayed. These are pretty
important fixes so I hope there's still time to get them to 4.20. But if
there's not time, please let me know and I'll pull these to
wireless-drivers-next.
All of these, expect the ath10k fix, have been in linux-next, and even
the ath10k fix was in the pending branch so it has been tested by the
kbuild bot.
I'll send the -next pull request tomorrow. Please let me know if there
are any problems.
Kalle
The following changes since commit 2e6e902d185027f8e3cb8b7305238f7e35d6a436:
Linux 4.20-rc4 (2018-11-25 14:19:31 -0800)
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-2018-12-19
for you to fetch changes up to 53884577fbcef33a7d15ad664e664a3dabe35171:
ath10k: skip sending quiet mode cmd for WCN3990 (2018-12-19 15:37:01 +0200)
----------------------------------------------------------------
wireless-drivers fixes for 4.20
Last set of fixes for 4.20. All (except the mt76 fix) of these are
important fixes to user reported problems and pretty small in size.
rtlwifi
* fix skb leak
mwifiex
* revert a commit from v4.19 due to problems with locking
mt76
* fix a potential NULL derenfence
* add entry to MAINTAINERS
iwlwifi
* fix a firmware crash which was a regression introduced in v4.20-rc4
ath10k
* fix a firmware crash with wcn3990 firmware
----------------------------------------------------------------
Brian Norris (1):
Revert "mwifiex: restructure rx_reorder_tbl_lock usage"
Emmanuel Grumbach (1):
iwlwifi: mvm: don't send GEO_TX_POWER_LIMIT to old firmwares
Larry Finger (1):
rtlwifi: Fix leak of skb when processing C2H_BT_INFO
Lorenzo Bianconi (2):
mt76: fix potential NULL pointer dereference in mt76_stop_tx_queues
mt76: add entry in MAINTAINERS file
Rakesh Pillai (1):
ath10k: skip sending quiet mode cmd for WCN3990
MAINTAINERS | 7 ++
drivers/net/wireless/ath/ath10k/core.c | 28 +++++++
drivers/net/wireless/ath/ath10k/debug.c | 5 +-
drivers/net/wireless/ath/ath10k/thermal.c | 9 ++
drivers/net/wireless/ath/ath10k/wmi-tlv.h | 3 +
drivers/net/wireless/ath/ath10k/wmi.h | 1 +
drivers/net/wireless/intel/iwlwifi/mvm/fw.c | 9 ++
drivers/net/wireless/marvell/mwifiex/11n.c | 5 +-
.../net/wireless/marvell/mwifiex/11n_rxreorder.c | 96 +++++++++++-----------
drivers/net/wireless/marvell/mwifiex/uap_txrx.c | 3 -
drivers/net/wireless/mediatek/mt76/tx.c | 7 +-
drivers/net/wireless/realtek/rtlwifi/base.c | 1 +
12 files changed, 118 insertions(+), 56 deletions(-)
next reply other threads:[~2018-12-19 14:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 14:34 Kalle Valo [this message]
2018-12-19 16:39 ` pull-request: wireless-drivers 2018-12-19 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=87bm5hvb51.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).