From: Luca Coelho <luca@coelho.fi>
To: kvalo@codeaurora.org
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH 03/12] iwlwifi: remove deprecated and unused iwl_mvm_keyinfo struct
Date: Sat, 18 Apr 2020 11:08:48 +0300 [thread overview]
Message-ID: <iwlwifi.20200418110539.93860da2d12a.Ifeca3b3313e3f14330317bc3e3d62f7d991ec955@changeid> (raw)
In-Reply-To: <20200418080857.2232093-1-luca@coelho.fi>
From: Luca Coelho <luciano.coelho@intel.com>
This struct hasn't been used in years and is just a remnant of an API
support removal that missed this structured.
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
---
.../net/wireless/intel/iwlwifi/fw/api/sta.h | 26 -------------------
1 file changed, 26 deletions(-)
diff --git a/drivers/net/wireless/intel/iwlwifi/fw/api/sta.h b/drivers/net/wireless/intel/iwlwifi/fw/api/sta.h
index 970e9e508ad0..c010e6febbf4 100644
--- a/drivers/net/wireless/intel/iwlwifi/fw/api/sta.h
+++ b/drivers/net/wireless/intel/iwlwifi/fw/api/sta.h
@@ -245,32 +245,6 @@ enum iwl_sta_sleep_flag {
#define STA_KEY_LEN_WEP40 (5)
#define STA_KEY_LEN_WEP104 (13)
-/**
- * struct iwl_mvm_keyinfo - key information
- * @key_flags: type &enum iwl_sta_key_flag
- * @tkip_rx_tsc_byte2: TSC[2] for key mix ph1 detection
- * @reserved1: reserved
- * @tkip_rx_ttak: 10-byte unicast TKIP TTAK for Rx
- * @key_offset: key offset in the fw's key table
- * @reserved2: reserved
- * @key: 16-byte unicast decryption key
- * @tx_secur_seq_cnt: initial RSC / PN needed for replay check
- * @hw_tkip_mic_rx_key: byte: MIC Rx Key - used for TKIP only
- * @hw_tkip_mic_tx_key: byte: MIC Tx Key - used for TKIP only
- */
-struct iwl_mvm_keyinfo {
- __le16 key_flags;
- u8 tkip_rx_tsc_byte2;
- u8 reserved1;
- __le16 tkip_rx_ttak[5];
- u8 key_offset;
- u8 reserved2;
- u8 key[16];
- __le64 tx_secur_seq_cnt;
- __le64 hw_tkip_mic_rx_key;
- __le64 hw_tkip_mic_tx_key;
-} __packed;
-
#define IWL_ADD_STA_STATUS_MASK 0xFF
#define IWL_ADD_STA_BAID_VALID_MASK 0x8000
#define IWL_ADD_STA_BAID_MASK 0x7F00
--
2.25.1
next prev parent reply other threads:[~2020-04-18 8:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 8:08 [PATCH 00/12] iwlwifi: updates intended for v5.8 2020-04-18 Luca Coelho
2020-04-18 8:08 ` [PATCH 01/12] iwlwifi: pcie: move iwl_pcie_ctxt_info_alloc_dma() to user Luca Coelho
2020-04-18 8:08 ` [PATCH 02/12] iwlwifi: mvm: add framework for specific phy configuration Luca Coelho
2020-04-18 8:08 ` Luca Coelho [this message]
2020-04-18 8:08 ` [PATCH 04/12] iwlwifi: remove fw_monitor module parameter Luca Coelho
2020-04-18 8:08 ` [PATCH 05/12] iwlwifi: acpi: read TAS table from ACPI and send it to the FW Luca Coelho
2020-04-18 8:08 ` [PATCH 06/12] iwlwifi: add new cards for AX family Luca Coelho
2020-04-18 8:08 ` [PATCH 07/12] iwlwifi: pcie: add cfgs for SoCs with device ID 0x4FD0 Luca Coelho
2020-04-18 8:08 ` [PATCH 08/12] iwlwifi: update few product names in AX family Luca Coelho
2020-04-18 8:08 ` [PATCH 09/12] iwlwifi: mvm: tell firmware about required LTR delay Luca Coelho
2020-04-18 8:08 ` [PATCH 10/12] iwlwifi: pcie: add new structure for Qu devices with medium latency Luca Coelho
2020-04-18 8:08 ` [PATCH 11/12] iwlwifi: pcie: add new structs for So devices with long latency Luca Coelho
2020-04-18 8:08 ` [PATCH 12/12] iwlwifi: debug: set NPK buffer in context info Luca Coelho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=iwlwifi.20200418110539.93860da2d12a.Ifeca3b3313e3f14330317bc3e3d62f7d991ec955@changeid \
--to=luca@coelho.fi \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).