From: Johannes Berg <johannes@sipsolutions.net>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: pull-request: mac80211 2017-05-23
Date: Tue, 23 May 2017 14:42:55 +0200 [thread overview]
Message-ID: <20170523124256.23463-1-johannes@sipsolutions.net> (raw)
Hi Dave,
I have just two fixes here, one of the scheduled scan issue that
Sander Eikelenboom found, and the other properly makes mesh more
strictly check its extension headers.
Please pull and let me know if there's any problem.
Thanks,
johannes
The following changes since commit 29cee56c0be46ad01e78af104a06223c65ee0c67:
Merge tag 'mac80211-for-davem-2017-05-08' of git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211 (2017-05-08 16:02:23 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-davem-2017-05-23
for you to fetch changes up to 1b57b6210f4e52904393be97c62122aae69bc8aa:
cfg80211: make cfg80211_sched_scan_results() work from atomic context (2017-05-23 14:36:46 +0200)
----------------------------------------------------------------
Just two fixes this time:
* fix the scheduled scan "BUG: scheduling while atomic"
* check mesh address extension flags more strictly
----------------------------------------------------------------
Arend Van Spriel (1):
cfg80211: make cfg80211_sched_scan_results() work from atomic context
Rajkumar Manoharan (1):
mac80211: strictly check mesh address extension mode
net/mac80211/rx.c | 3 ++-
net/wireless/scan.c | 8 ++++----
net/wireless/util.c | 10 ++++++----
3 files changed, 12 insertions(+), 9 deletions(-)
next reply other threads:[~2017-05-23 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 12:42 Johannes Berg [this message]
2017-05-24 19:32 ` pull-request: mac80211 2017-05-23 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=20170523124256.23463-1-johannes@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--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