summaryrefslogtreecommitdiffstats
path: root/mm/page_owner.c
diff options
context:
space:
mode:
authorBob Copeland <me@bobcopeland.com>2015-12-19 09:59:37 -0500
committerJohannes Berg <johannes.berg@intel.com>2016-01-14 11:10:17 +0100
commit354210f8046cc801d6001f10c5c32967932b09a2 (patch)
treee119e4bb6263141e04ec712cf8dea8971d971184 /mm/page_owner.c
parentb9f628fcc673ba582cc7a17c4fd9be01133e61bd (diff)
downloadop-kernel-dev-354210f8046cc801d6001f10c5c32967932b09a2.zip
op-kernel-dev-354210f8046cc801d6001f10c5c32967932b09a2.tar.gz
Revert "mac80211_hwsim: support any address in userspace"
This reverts commit cd37a90b2a417e5882414e19954eeed174aa4d29. Different userspace programs interpreted HWSIM_ATTR_ADDR_TRANSMITTER and HWSIM_ATTR_ADDR_RECEIVER differently: some expected it to be an unchanging hardware address that is tied to the radio despite which address is configured on the interface, while others expected to be a copy of the address in the frame (the configured address). The intent of the original authors is unclear. The latter interpretation doesn't really work properly with multiple vifs and broadcast frames. Also, as the TA is already in the frame, userspace programs can actually support configured addresses in the former interpretation by mapping between them and the supplied HWSIM_ATTR_ADDR_TRANSMITTER. So, in the interest of API stability, revert to the previous mode of operation and going forward use the former interpretation. Signed-off-by: Bob Copeland <me@bobcopeland.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'mm/page_owner.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud