linux-kernel - Re: [PATCH ath-next 0/4] wifi: ath11k: add support for Tx Power insertion

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <176122821156.3033388.10937600819458906745.b4-ty@oss.qualcomm.com>
Date: Thu, 23 Oct 2025 07:03:31 -0700
From: Jeff Johnson <jeff.johnson@....qualcomm.com>
To: Jeff Johnson <jjohnson@...nel.org>,
        Aditya Kumar Singh <aditya.kumar.singh@....qualcomm.com>
Cc: linux-wireless@...r.kernel.org, ath11k@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH ath-next 0/4] wifi: ath11k: add support for Tx Power
 insertion


On Fri, 17 Oct 2025 09:37:56 +0530, Aditya Kumar Singh wrote:
> For certain action frames like the TPC Report IE in the spectrum management
> TPC Report action frame, and in the Radio Measurement Link Measurement
> Report action frame there is a requirement to fill in the current
> and max Tx power of the device in the packet.
> 
> Add support to populate these fields in the relevant packets. Advertise
> this capability from the driver using the feature flag
> NL80211_FEATURE_TX_POWER_INSERTION.
> 
> [...]

Applied, thanks!

[1/4] wifi: ath11k: relocate some Tx power related functions in mac.c
      commit: 66887282233d281cd9109dabfdad5d86b709acc0
[2/4] wifi: ath11k: wrap ath11k_mac_op_get_txpower() with lock-aware internal helper
      commit: c243d5e44f6ecbb29bf55b82e6dd92bca4fde0b1
[3/4] wifi: ath11k: add support for Tx Power insertion in RRM action frame
      commit: 722015690f52d046ae609e1b90cd3f018644d93d
[4/4] wifi: ath11k: advertise NL80211_FEATURE_TX_POWER_INSERTION
      commit: 998c68e96c03f10dec19b65279ade9d4000d1ae9

Best regards,
-- 
Jeff Johnson <jeff.johnson@....qualcomm.com>