From: David Heidelberg <david@ixit.cz>
To: Richard Acayan <mailingradian@gmail.com>,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: Jeff Johnson <jjohnson@kernel.org>,
Johannes Berg <johannes.berg@intel.com>,
Kalle Valo <kvalo@qca.qualcomm.com>,
Michal Kazior <michal.kazior@tieto.com>,
linux-wireless@vger.kernel.org, ath10k@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org
Subject: Re: [PATCH RFC v2] wifi: ath10k: make in-order rx amsdu buffers persistent
Date: Fri, 31 Jul 2026 16:55:20 +0200 [thread overview]
Message-ID: <d8d818fa-dac3-4200-a8bb-e6d664725783@ixit.cz> (raw)
In-Reply-To: <amyzhVgSeYO6MptG@rdacayan>
On 31/07/2026 16:39, Richard Acayan wrote:
[...]
>>>
>>> + msdu = skb_peek(list);
>>> + rxd = HTT_RX_BUF_TO_RX_DESC(hw,
>>> + (void *)msdu->data - hw->rx_desc_ops->rx_desc_size);
>>
>> Dead rxd computation before the loop — VALID, MINOR
>>
>> Lines 3168–3170 compute rxd via skb_peek(), but the while loop at 3172
>> immediately dequeues the same SKB and unconditionally recomputes rxd at lines
>> 3175–3177. The pre-loop assignment is never read. It's dead code. The original
>> patch must have introduced this when restructuring (the pre-existing code
>> likely used rxd from before the loop). It should be removed.
>
> This was removed on 20 January 2026 before v1 was submitted. It seems
> this v2 is based on applying the commits to the pre-2026 patch.
I checked against what Comma.AI uses, and it's also gone there, so we've been
using pre-v1 in sdm845-next.
Dropping it definitely make sense, and since Comma.AI already tested, I assume
no regression.
Will be addressed in v3.
David
prev parent reply other threads:[~2026-07-31 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 21:45 [PATCH RFC v2] wifi: ath10k: make in-order rx amsdu buffers persistent David Heidelberg via B4 Relay
2026-07-21 10:39 ` David Heidelberg
2026-07-31 2:24 ` Jeff Johnson
2026-07-31 6:33 ` Johannes Berg
2026-07-31 14:39 ` Richard Acayan
2026-07-31 14:55 ` David Heidelberg [this message]
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=d8d818fa-dac3-4200-a8bb-e6d664725783@ixit.cz \
--to=david@ixit.cz \
--cc=ath10k@lists.infradead.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=johannes.berg@intel.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mailingradian@gmail.com \
--cc=michal.kazior@tieto.com \
--cc=phone-devel@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