From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: netdev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-wireless
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: pull-request: mac80211 2015-12-15
Date: Tue, 15 Dec 2015 13:30:21 +0100 [thread overview]
Message-ID: <1450182621.3356.12.camel@sipsolutions.net> (raw)
Hi Dave,
After going through my patch queue, I have another set of fixes that I
think is still appropriate for the current cycle.
Two of my own restart changes there are fairly big but for the most
part just move code around so it can be called in a slightly different
order.
Let me know if there are any issues.
Thanks,
johannes
The following changes since commit c1df932c0574c13ab3ce72e969c9647ff3aaad68:
mac80211: fix off-channel mgmt-tx uninitialized variable usage (2015-12-02 22:27:53 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211.git tags/mac80211-for-davem-2015-12-15
for you to fetch changes up to cf1e05c63642ce65821a6277adfc2157f7334c9d:
mac80211: handle width changes from opmode notification IE in beacon (2015-12-15 13:16:47 +0100)
----------------------------------------------------------------
Another set of fixes:
* memory leak fixes (from Ola)
* operating mode notification spec compliance fix (from Eyal)
* copy rfkill names in case pointer becomes invalid (myself)
* two hardware restart fixes (myself)
* get rid of "limiting TX power" log spam (myself)
----------------------------------------------------------------
Eyal Shapira (1):
mac80211: handle width changes from opmode notification IE in beacon
Johannes Berg (4):
rfkill: copy the name into the rfkill struct
mac80211: run scan completed work on reconfig failure
mac80211: reprogram in interface order
mac80211: suppress unchanged "limiting TX power" messages
Ola Olsson (3):
nl80211: fix a few memory leaks in reg.c
nl80211: Fix potential memory leak in nl80211_set_wowlan
nl80211: Fix potential memory leak in nl80211_connect
net/mac80211/cfg.c | 3 +-
net/mac80211/ieee80211_i.h | 4 +-
net/mac80211/mlme.c | 17 ++++---
net/mac80211/rx.c | 3 +-
net/mac80211/util.c | 113 +++++++++++++++++++++++++--------------------
net/mac80211/vht.c | 10 ++--
net/rfkill/core.c | 6 +--
net/wireless/nl80211.c | 5 +-
net/wireless/reg.c | 5 +-
9 files changed, 92 insertions(+), 74 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-12-15 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 12:30 Johannes Berg [this message]
2015-12-16 23:34 ` pull-request: mac80211 2015-12-15 David Miller
[not found] ` <20151216.183443.615368179590575650.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2015-12-17 12:44 ` Johannes Berg
2015-12-17 17:04 ` David Miller
2015-12-17 18:10 ` David Rivshin (Allworx)
[not found] ` <1450356272.8247.31.camel-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
2015-12-17 19:11 ` Joe Perches
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=1450182621.3356.12.camel@sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).