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-07-31
Date: Tue, 31 Jul 2018 13:48:15 +0300 [thread overview]
Message-ID: <87bmanadg0.fsf@kamboji.qca.qualcomm.com> (raw)
Hi Dave,
two small patches I still would like to get to the net tree for v4.18.
Please let me know if you have any problems.
Kalle
The following changes since commit 144fe2bfd236dc814eae587aea7e2af03dbdd755:
sock: fix sg page frag coalescing in sk_alloc_sg (2018-07-23 21:28:45 -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-2018-07-31
for you to fetch changes up to 299b6365a3b7cf7f5ea1c945a420e9ee4841d6f7:
brcmfmac: fix regression in parsing NVRAM for multiple devices (2018-07-25 10:30:36 +0300)
----------------------------------------------------------------
wireless-drivers fixes for 4.18
Last set of fixes before 4.18 is released
iwlwifi
* add new IDs for cards already available on the market
brcmfmac
* fix a regression introduced in v4.17
----------------------------------------------------------------
Emmanuel Grumbach (1):
iwlwifi: add more card IDs for 9000 series
Rafał Miłecki (1):
brcmfmac: fix regression in parsing NVRAM for multiple devices
.../wireless/broadcom/brcm80211/brcmfmac/pcie.c | 3 +-
drivers/net/wireless/intel/iwlwifi/cfg/9000.c | 69 ++++++++++++++++++++++
drivers/net/wireless/intel/iwlwifi/iwl-config.h | 5 ++
drivers/net/wireless/intel/iwlwifi/pcie/drv.c | 22 +++++++
4 files changed, 98 insertions(+), 1 deletion(-)
--
Kalle Valo
next reply other threads:[~2018-07-31 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 10:48 Kalle Valo [this message]
2018-07-31 17:34 ` pull-request: wireless-drivers 2018-07-31 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=87bmanadg0.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).