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-03-02
Date: Thu, 02 Mar 2017 11:15:42 +0200 [thread overview]
Message-ID: <87r32g9gzl.fsf@kamboji.qca.qualcomm.com> (raw)
Hi Dave,
only one patch this time, the new version of ath10k patch we reverted
earlier. I was supposed to send you this earlier but it got delayed
because I'm on vacation, so sorry about that. I'm hoping this is ok to
take also even the merge window is closed as the changes to the first
version of the patch are minimal.
Please let me know if there are any problems.
Kalle
The following changes since commit 8313064c2e75542201e557e2b496668811c2484a:
Merge tag 'nfsd-4.11' of git://linux-nfs.org/~bfields/linux (2017-02-28 15:39:09 -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-2017-03-02
for you to fetch changes up to 1657b8f84ed9fc1d2a100671f1d42d6286f20073:
ath10k: search SMBIOS for OEM board file extension (2017-03-02 10:48:41 +0200)
----------------------------------------------------------------
wireless-drivers fixes for 4.11
Add back a fixed version of an ath10k patch which was reverted during
the merge window.
----------------------------------------------------------------
Waldemar Rymarkiewicz (1):
ath10k: search SMBIOS for OEM board file extension
drivers/net/wireless/ath/ath10k/core.c | 101 ++++++++++++++++++++++++++++++++-
drivers/net/wireless/ath/ath10k/core.h | 19 +++++++
2 files changed, 117 insertions(+), 3 deletions(-)
--
Kalle Valo
next reply other threads:[~2017-03-02 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 9:15 Kalle Valo [this message]
2017-03-02 22:39 ` pull-request: wireless-drivers 2017-03-02 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=87r32g9gzl.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).