From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Saikiran B <bjsaikiran@gmail.com>,
Baochen Qiang <baochen.qiang@oss.qualcomm.com>
Cc: ath12k@lists.infradead.org, linux-wireless@vger.kernel.org,
kvalo@kernel.org
Subject: Re: [PATCH v2 2/2] wifi: ath12k: Fix firmware stats leak when pdev list is empty
Date: Fri, 30 Jan 2026 06:27:28 -0800 [thread overview]
Message-ID: <b96b9fb2-3313-4c3d-b20f-ea477f72bd62@oss.qualcomm.com> (raw)
In-Reply-To: <CAAFDt1uSQce_9AG2488yaeeEjCwQwQubW51K51VHiJF8Rp6xRQ@mail.gmail.com>
On 1/29/2026 11:32 PM, Saikiran B wrote:
> I have merged the tag, applied your patches and I can confirm that the
> leak has been fixed.
When I apply the patches would you like me to add the following?
Tested-by: Saikiran B <bjsaikiran@gmail.com>
next prev parent reply other threads:[~2026-01-30 14:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 9:52 [PATCH v2 0/2] wifi: ath12k: Fix 5GHz issues on WCN7850 Saikiran
2026-01-26 9:52 ` [PATCH v2 1/2] wifi: ath12k: Remove frequency range filtering for single-phy devices Saikiran
2026-01-27 3:22 ` Baochen Qiang
2026-01-27 4:04 ` Saikiran B
2026-01-27 7:41 ` Baochen Qiang
2026-01-27 8:58 ` Saikiran B
2026-01-27 10:21 ` Baochen Qiang
2026-01-27 19:06 ` Saikiran B
2026-01-26 9:52 ` [PATCH v2 2/2] wifi: ath12k: Fix firmware stats leak when pdev list is empty Saikiran
2026-01-27 3:27 ` Baochen Qiang
2026-01-27 4:17 ` Saikiran B
2026-01-27 4:40 ` Saikiran B
2026-01-29 2:27 ` Baochen Qiang
2026-01-29 14:06 ` Saikiran B
2026-01-30 2:09 ` Baochen Qiang
2026-01-30 7:32 ` Saikiran B
2026-01-30 7:50 ` Baochen Qiang
2026-01-30 14:27 ` Jeff Johnson [this message]
2026-01-30 16:45 ` Saikiran B
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=b96b9fb2-3313-4c3d-b20f-ea477f72bd62@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=ath12k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=bjsaikiran@gmail.com \
--cc=kvalo@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