Searched hist:baf41bc35f2bdb953da532645fd82009c2d12acf (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/mvm/ |
| H A D | rx.c | diff baf41bc35f2bdb953da532645fd82009c2d12acf Wed Sep 13 08:46:14 CDT 2017 Shaul Triebitz <shaul.triebitz@intel.com> iwlwifi: mvm: do not print security error in monitor mode
In monitor mode we are not expected to decrypt encrypted
packets (not having the keys).
Hence we are expected to get an unknown rx security status.
Keeping the print in monitor mode causes a print for each
captured packet flooding the dmesg.
Signed-off-by: Shaul Triebitz <shaul.triebitz@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
|
| H A D | rxmq.c | diff baf41bc35f2bdb953da532645fd82009c2d12acf Wed Sep 13 08:46:14 CDT 2017 Shaul Triebitz <shaul.triebitz@intel.com> iwlwifi: mvm: do not print security error in monitor mode
In monitor mode we are not expected to decrypt encrypted
packets (not having the keys).
Hence we are expected to get an unknown rx security status.
Keeping the print in monitor mode causes a print for each
captured packet flooding the dmesg.
Signed-off-by: Shaul Triebitz <shaul.triebitz@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
|
| H A D | mvm.h | diff baf41bc35f2bdb953da532645fd82009c2d12acf Wed Sep 13 08:46:14 CDT 2017 Shaul Triebitz <shaul.triebitz@intel.com> iwlwifi: mvm: do not print security error in monitor mode
In monitor mode we are not expected to decrypt encrypted
packets (not having the keys).
Hence we are expected to get an unknown rx security status.
Keeping the print in monitor mode causes a print for each
captured packet flooding the dmesg.
Signed-off-by: Shaul Triebitz <shaul.triebitz@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
|
| H A D | mac80211.c | diff baf41bc35f2bdb953da532645fd82009c2d12acf Wed Sep 13 08:46:14 CDT 2017 Shaul Triebitz <shaul.triebitz@intel.com> iwlwifi: mvm: do not print security error in monitor mode
In monitor mode we are not expected to decrypt encrypted
packets (not having the keys).
Hence we are expected to get an unknown rx security status.
Keeping the print in monitor mode causes a print for each
captured packet flooding the dmesg.
Signed-off-by: Shaul Triebitz <shaul.triebitz@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
|