From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: pull-request: mac80211-next 2013-08-16
Date: Fri, 16 Aug 2013 13:01:12 +0200 [thread overview]
Message-ID: <1376650872.15299.20.camel@jlt4.sipsolutions.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 3521 bytes --]
John,
And another set of patches for -next :-)
This time I have various improvements all over the place: IBSS, mesh,
testmode, AP client powersave handling, one of the rare rfkill patches
and some code cleanup.
Let me know if there's any problem.
johannes
The following changes since commit 73da7d5bab79ad7e16ff44d67c3fe8b9c0b33e5b:
mac80211: add channel switch command and beacon callbacks (2013-08-01 18:30:33 +0200)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git for-john
for you to fetch changes up to 27b3eb9c06a7193bdc9800cd00764a130343bc8a:
mac80211: add APIs to allow keeping connections after WoWLAN (2013-08-16 12:58:43 +0200)
----------------------------------------------------------------
Antonio Quartulli (1):
mac80211: ibss - do not scan if not needed when creating an IBSS
Chun-Yeow Yeoh (1):
mac80211: allow lowest basic rate for unicast management for mesh
David Spinadel (2):
cfg80211: add wdev to testmode cmd
mac80211: add vif to testmode cmd
Johan Almbladh (1):
mac80211: perform power save processing before decryption
Johannes Berg (4):
wireless: make TU conversion macros available
nl80211: clean up CQM settings code
mac80211: add control port protocol TX control flag
mac80211: add APIs to allow keeping connections after WoWLAN
Luis Henriques (1):
net: rfkill: Do not ignore errors from regulator_enable()
Simon Wunderlich (2):
mac80211: fix ieee80211_sta_process_chanswitch for 5/10 MHz channels
mac80211: move ibss presp generation in own function
Documentation/DocBook/80211.tmpl | 1 +
drivers/net/wireless/ath/ath6kl/testmode.c | 3 +-
drivers/net/wireless/ath/ath6kl/testmode.h | 7 +-
.../net/wireless/brcm80211/brcmfmac/wl_cfg80211.c | 4 +-
drivers/net/wireless/iwlwifi/dvm/tx.c | 2 +-
drivers/net/wireless/iwlwifi/iwl-devtrace.h | 7 +-
drivers/net/wireless/iwlwifi/mvm/time-event.c | 7 +-
drivers/net/wireless/iwlwifi/mvm/tx.c | 9 +-
drivers/net/wireless/mac80211_hwsim.c | 1 +
drivers/net/wireless/ti/wlcore/testmode.c | 3 +-
drivers/net/wireless/ti/wlcore/testmode.h | 3 +-
include/linux/ieee80211.h | 4 +
include/net/cfg80211.h | 5 +-
include/net/mac80211.h | 109 +++++-
net/mac80211/cfg.c | 15 +-
net/mac80211/ibss.c | 196 ++++++----
net/mac80211/ieee80211_i.h | 3 -
net/mac80211/key.c | 154 +++++++-
net/mac80211/mlme.c | 9 +
net/mac80211/rate.c | 23 +-
net/mac80211/rc80211_minstrel_ht.c | 5 +-
net/mac80211/rx.c | 404 ++++++++++-----------
net/mac80211/tx.c | 8 +-
net/mac80211/util.c | 2 +-
net/rfkill/rfkill-regulator.c | 8 +-
net/wireless/nl80211.c | 74 ++--
net/wireless/rdev-ops.h | 5 +-
net/wireless/trace.h | 8 +-
28 files changed, 707 insertions(+), 372 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next reply other threads:[~2013-08-16 11:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 11:01 Johannes Berg [this message]
2013-08-16 18:26 ` pull-request: mac80211-next 2013-08-16 John W. Linville
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=1376650872.15299.20.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).