Remove following unused suite and update test control files as needed...
wifi_matfunc_bcm4356
wifi_matfunc_intel7265
wifi_matfunc_marvell8897
wifi_perf_bcm4356
wifi_perf_intel7265
wifi_perf_marvell8897
wifi_correctness_cros_core
wifi_matfunc_arc
I suppose we could put network_WiFi_RegDomain in wifi_matfunc, to see how it runs...or maybe wifi_flaky would be better, now that it should be running again soon.
The test looks to hardcode some stuff for individual drivers/devices, so it's a bit high-maintenance. It's also quite possibly out of date. But at least putting it into something that runs regularly will help us evaluate whether to kill it entirely. If it *can* be made to work right, it might be one step toward getting real coverage of our regulatory change mechanisms.
Comment 1 by harpreet@chromium.org
, May 10 2018