Hi, In preparation for FORTIFY_SOURCE performing compile-time and run-time field bounds checking for memcpy(), memmove(), and memset(), avoid intentionally writing across neighboring fields. In this case, there is a lot of redundant struct member declarations, and everything can be made smaller, more description, and drop a field-spanning memcpy() call all at the same time. The result is no warning from the future FORTIFY_SOURCE and identical machine code. Thanks, -Kees Kees Cook (2): staging: wlan-ng: Remove pointless a3/a4 union staging: wlan-ng: Avoid duplicate header in tx/rx frames drivers/staging/wlan-ng/hfa384x.h | 19 ++-------- drivers/staging/wlan-ng/hfa384x_usb.c | 13 ++++--- drivers/staging/wlan-ng/p80211conv.c | 48 +++++++++++++------------- drivers/staging/wlan-ng/p80211conv.h | 2 +- drivers/staging/wlan-ng/p80211hdr.h | 30 +++++----------- drivers/staging/wlan-ng/p80211mgmt.h | 24 ++++++------- drivers/staging/wlan-ng/p80211netdev.c | 12 +++---- drivers/staging/wlan-ng/p80211netdev.h | 2 +- drivers/staging/wlan-ng/prism2sta.c | 6 ++-- 9 files changed, 64 insertions(+), 92 deletions(-) -- 2.30.2
