diff options
| author | Sergey Matyukevich <sergey.matyukevich.os@quantenna.com> | 2020-04-24 14:29:04 +0300 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2020-05-27 11:02:02 +0300 |
| commit | c03369558c435f7e82f7c06b0173fa73c1ed15c0 (patch) | |
| tree | 0f8775a116c2a9a889f8730c66dac752b71faf5b /lib/pm-notifier-error-inject.c | |
| parent | 33462e68231bccfe563a87614f4c4dd5d333837c (diff) | |
| download | linux-c03369558c435f7e82f7c06b0173fa73c1ed15c0.tar.xz | |
nl80211: simplify peer specific TID configuration
Current rule for applying TID configuration for specific peer looks overly
complicated. No need to reject new TID configuration when override flag is
specified. Another call with the same TID configuration, but without
override flag, allows to apply new configuration anyway.
Use the same approach as for the 'all peers' case: if override flag is
specified, then reset existing TID configuration and immediately
apply a new one.
Signed-off-by: Sergey Matyukevich <sergey.matyukevich.os@quantenna.com>
Link: https://lore.kernel.org/r/20200424112905.26770-5-sergey.matyukevich.os@quantenna.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'lib/pm-notifier-error-inject.c')
0 files changed, 0 insertions, 0 deletions