From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Greg,
Thanks for merging the last set. I starting going through the code
again, and removed a pile of dead code (patches 1-7).
However in the process I noticed a couple of cases where raw beacon
frame information was copied to a new wlan network struct, but the
retrieved information wasn't, which can leave to trying to access the
network with parameters that do not match that of the access point
(patches 8-9).
There is also a fix for a case where we in AP mode would send out a
corrupted frame on the wire (patch 10).
Patch 11 is a simple cleanup.
It would be nice if it can all make it into staging-next, but if not,
8, 9, and 10 are rather serious and really need to go in.
Thanks,
Jes
Jes Sorensen (11):
staging: rtl8723au: struct mlme_priv->wps_beacon_ie is never set
staging: rtl8723au: Remove unused mlme_priv->wps_assoc_resp_ie and
friends
staging: rtl8723au: Remove unused struct mlme_priv->wps_probe_resp_ie
staging: rtl8723au: Remove obsolete mlme_priv->p2p_* entries
staging: rtl8723au: Remove unused struct mlme_priv->wfd_* entries
staging: rtl8723au: Remove write-only struct
security_priv->authenticator_ie
staging: rtl8723au: Remove (hopefully) last duplicate define of
WLAN_EID_RSN
staging: rtl8723au: rtw_survey_event_cb23a(): Remember to clone beacon
data
staging: rtl8723au: rtw_joinbss_update_network23a(): update beacon
info as well
staging: rtl8723au: issue_probersp(): Don't insert beacon data twice
staging: rtl8723au: issue_probersp(): No need to calculate location of
IEs, we know where they are
drivers/staging/rtl8723au/core/rtw_ap.c | 61 +----------------
drivers/staging/rtl8723au/core/rtw_cmd.c | 13 ----
drivers/staging/rtl8723au/core/rtw_ieee80211.c | 2 +-
drivers/staging/rtl8723au/core/rtw_mlme.c | 49 +++++--------
drivers/staging/rtl8723au/core/rtw_mlme_ext.c | 87 ++----------------------
drivers/staging/rtl8723au/include/rtw_mlme.h | 28 --------
drivers/staging/rtl8723au/include/rtw_security.h | 3 -
7 files changed, 27 insertions(+), 216 deletions(-)
--
1.9.3
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
