From: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
To: christophergriffin05@gmail.com, Jeff Johnson <jjohnson@kernel.org>
Cc: Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
ath12k@lists.infradead.org, linux-kernel@vger.kernel.org,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/2] wifi: ath: simplify copying a peer's PPE thresholds
Date: Sat, 14 Nov 2026 00:25:16 +0530 [thread overview]
Message-ID: <03e7af46-7fcd-445e-9210-395bbb8b5410@oss.qualcomm.com> (raw)
In-Reply-To: <20261110-ath-peer-ppe-thres-loop-v2-0-fced87507920@gmail.com>
On 11/10/2026 8:07 PM, Christopher Griffin via B4 Relay wrote:
> Rameshkumar suggested this while reviewing the PPE threshold bit-order
> fix [1]: the loop that copies a peer's PPE thresholds into the WMI
> layout shifts each bit in from the top, where it can put it in place.
> ath11k and ath12k carry the same loop, so one patch each. No functional
> change; the patches don't depend on the bit-order series.
>
> Compile tested only (W=1, both drivers). A userspace copy of the old
> and the new loop gives the same output for every 6-bit value in every
> RU slot.
>
> The patches, this letter and that test were written with Claude, an AI
> coding assistant.
>
> [1] https://lore.kernel.org/all/b60c4c56-483b-406e-92ab-643b0fdf2dc8@oss.qualcomm.com/
>
> ---
> Changes in v2:
> - Dropped the paragraph about the equivalence test from both changelogs
> (Rameshkumar).
> - Kept the one-line note on AI use in the changelogs:
> Documentation/process/generated-content.rst asks for it in changelogs
> and cover letters.
> - Rebased on ath-next.
> - Link to v1: https://patch.msgid.link/20261106-ath-peer-ppe-thres-loop-v1-0-f6bb5fe9ffb3@gmail.com
>
> ---
> Christopher Griffin (2):
> wifi: ath11k: simplify copying a peer's PPE thresholds
> wifi: ath12k: simplify copying a peer's PPE thresholds
>
> drivers/net/wireless/ath/ath11k/mac.c | 3 +--
> drivers/net/wireless/ath/ath12k/mac.c | 3 +--
> 2 files changed, 2 insertions(+), 4 deletions(-)
> ---
> base-commit: d0fbb39d65dc9dcb4175fa6b23e473dec3670f4d
> change-id: 20261106-ath-peer-ppe-thres-loop-ce5c2b2e68e1
>
Reviewed-by: Rameshkumar Sundaram <rameshkumar.sundaram@oss.qualcomm.com>
prev parent reply other threads:[~2026-11-13 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 14:37 Christopher Griffin via B4 Relay
2026-11-10 14:37 ` [PATCH v2 1/2] wifi: ath11k: " Christopher Griffin via B4 Relay
2026-11-10 14:37 ` [PATCH v2 2/2] wifi: ath12k: " Christopher Griffin via B4 Relay
2026-11-13 18:55 ` Rameshkumar Sundaram [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=03e7af46-7fcd-445e-9210-395bbb8b5410@oss.qualcomm.com \
--to=rameshkumar.sundaram@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=christophergriffin05@gmail.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®