mirror of https://lore.kernel.org/ath12k/
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: Aditya Kumar Singh <aditya.kumar.singh@oss.qualcomm.com>,
	 Remi Pommarel <repk@triplefau.lt>,
	 ath12k@lists.infradead.org, linux-wireless@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	 Jeff Johnson <jjohnson@kernel.org>
Subject: Re: [PATCH v2] wifi: ath12k: remove return for empty tx bitrate in mac_op_sta_statistics
Date: Fri, 31 Jan 2025 18:46:49 +0200	[thread overview]
Message-ID: <874j1fgccm.fsf@kernel.org> (raw)
In-Reply-To: <a1a65ff7-bb5c-4c90-98b6-7155b58e89c0@oss.qualcomm.com> (Jeff Johnson's message of "Thu, 30 Jan 2025 10:57:30 -0800")

Jeff Johnson <jeff.johnson@oss.qualcomm.com> writes:

> On 1/30/2025 1:18 AM, Aditya Kumar Singh wrote:
>
>> On 1/30/25 14:19, Remi Pommarel wrote:
>>> On Thu, Jan 30, 2025 at 12:21:54PM +0530, Aditya Kumar Singh wrote:
>>>> On 1/29/25 22:25, Remi Pommarel wrote:
>>>>> Currently in ath12k_mac_op_sta_statistics() there is the following
>>>>> logic:
>>>>>
>>>>>       if (!arsta->txrate.legacy && !arsta->txrate.nss)
>>>>>           return;
>>>>>
>>>>> Because ath12k_sta_statistics is used to report many info to iw wlan0 link,
>>>>> if it return for empty legacy and nss of arsta->txrate, then the other
>>>>> stats after it will not be set.
>>>>>
>>>>> To address this issue remove the return and instead invert the logic to set
>>>>> the txrate logic if (arsta->txrate.legacy || arsta->txrate.nss).
>>>>>
>>>>> The same was done also in both ath10k with commit 1cd6ba8ae33e ("ath10k:
>>>>> remove return for NL80211_STA_INFO_TX_BITRATE") and ath11k as well with
>>>>> commit 1d795645e1ee ("ath11k: remove return for empty tx bitrate in
>>>>> mac_op_sta_statistics").
>>>>>
>>>>> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1
>>>>
>>>> MISSING_BLANK_LINE
>>>> 'Tested-on:' tag missing blank line after it.
>>>>
>>>> You missed v1 comment? :)
>>>
>>> Yes sorry I think your mail never reached me, did you CC me ? Do you
>>> need a respin ?
>>>
>> 
>> No problem. No need of respin just because of this. I think Jeff can fix 
>> in pending?
>> 
>> It's strange that the v1 reply appears to be delivered from my mail box 
>> and it is sent to the list. I see even Jeff replying to that. But none 
>> of those are captured in patchwork. Not sure.
>
> it was only sent to the ath12k list
> perhaps you need to include linux-wireless@vger.kernel.org

Yeah, patchwork only follows linux-wireless.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


  parent reply	other threads:[~2025-01-31 16:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 16:55 [PATCH v2] wifi: ath12k: remove return for empty tx bitrate in mac_op_sta_statistics Remi Pommarel
2025-01-30  6:51 ` Aditya Kumar Singh
2025-01-30  8:49   ` Remi Pommarel
2025-01-30  9:18     ` Aditya Kumar Singh
2025-01-30 18:57       ` Jeff Johnson
2025-01-31  3:55         ` Aditya Kumar Singh
2025-01-31 16:46         ` Kalle Valo [this message]
2025-01-31 19:34 ` Jeff Johnson

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=874j1fgccm.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=aditya.kumar.singh@oss.qualcomm.com \
    --cc=ath12k@lists.infradead.org \
    --cc=jeff.johnson@oss.qualcomm.com \
    --cc=jjohnson@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=repk@triplefau.lt \
    /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