diff options
| author | Johannes Berg <johannes.berg@intel.com> | 2024-12-27 10:00:57 +0200 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2025-01-13 14:01:51 +0100 |
| commit | 193aa7eee2975fec7b5e224a53862c36b5500bd8 (patch) | |
| tree | 73329536dbbe034661e30e35fab0a7badf8a21e8 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | wifi: iwlwifi: differentiate NIC error types (diff) | |
| download | linux-193aa7eee2975fec7b5e224a53862c36b5500bd8.tar.gz linux-193aa7eee2975fec7b5e224a53862c36b5500bd8.zip | |
wifi: iwlwifi: mvm: remove warning on unallocated BAID
Due to the firmware allocating the BAID, we can only install
the data structure after the BAID is valid from the firmware's
point of view. As a result, the firmware can start sending
frame release notifications to the driver immediately. This
isn't supposed to happen by protocol, since the peer STA is
not expected to use the blockack session until the AddBA has
a response. However, firmware doesn't know that, our RX path
can't know when it was, so simply don't WARN in this case but
only have a debug message.
Since the BAID comes from firmware, also use IWL_FW_CHECK()
instead of a warning for the validity check.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://patch.msgid.link/20241227095718.4360f2b9e185.I447f9a5fc6dfdc78ec238200338e2da040ee7e61@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions