From: Kalle Valo <kvalo@codeaurora.org>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: wireless-drivers-2020-03-25
Date: Wed, 25 Mar 2020 19:57:54 +0000 (UTC) [thread overview]
Message-ID: <20200325195754.92C97C433D2@smtp.codeaurora.org> (raw)
Hi,
here's a pull request to net tree, more info below. Please let me know if there
are any problems.
Kalle
The following changes since commit e2e57291097b289f84e05fa58ab5e6c6f30cc6e2:
wlcore: remove stray plus sign (2020-03-12 18:48:14 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers.git tags/wireless-drivers-2020-03-25
for you to fetch changes up to 0433ae556ec8fb588a0735ddb09d3eb9806df479:
iwlwifi: don't send GEO_TX_POWER_LIMIT if no wgds table (2020-03-23 18:38:03 +0200)
----------------------------------------------------------------
wireless-drivers fixes for v5.6
Fourth, and last, set of fixes for v5.6. Just two important fixes to
iwlwifi regressions.
iwlwifi
* fix GEO_TX_POWER_LIMIT command on certain devices which caused
firmware to crash during initialisation
* add back device ids for three devices which were accidentally
removed
----------------------------------------------------------------
Golan Ben Ami (1):
iwlwifi: don't send GEO_TX_POWER_LIMIT if no wgds table
Luca Coelho (1):
iwlwifi: pcie: add 0x2526/0x401* devices back to cfg detection
drivers/net/wireless/intel/iwlwifi/fw/acpi.c | 14 ++++++++------
drivers/net/wireless/intel/iwlwifi/fw/acpi.h | 14 ++++++++------
drivers/net/wireless/intel/iwlwifi/mvm/fw.c | 9 ++++++++-
drivers/net/wireless/intel/iwlwifi/pcie/drv.c | 3 +++
4 files changed, 27 insertions(+), 13 deletions(-)
next reply other threads:[~2020-03-25 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 19:57 Kalle Valo [this message]
2020-03-25 20:12 ` pull-request: wireless-drivers-2020-03-25 David Miller
2020-03-26 6:19 ` Kalle Valo
2020-03-26 18:29 ` David Miller
2020-03-26 19:38 ` Kalle Valo
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=20200325195754.92C97C433D2@smtp.codeaurora.org \
--to=kvalo@codeaurora.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).