From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
quic_bqiang@quicinc.com, Jeff Johnson <jjohnson@kernel.org>
Cc: usama.anjum@collabora.com, kernel@collabora.com,
linux-wireless@vger.kernel.org, ath11k@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5] wifi: ath11k: Fix memory reuse logic
Date: Tue, 6 May 2025 18:10:48 +0500 [thread overview]
Message-ID: <ec0bb100-4a70-4827-86b1-e4a7e8867a2d@collabora.com> (raw)
In-Reply-To: <f58075f7-f643-4e47-b774-dc529aaa01e5@oss.qualcomm.com>
On 5/6/25 12:17 AM, Jeff Johnson wrote:
> v2 feedback was not incorporated:
> For starters, can we make the subject a bit more specific, i.e.
> Fix MHI target memory reuse logic
>
> But don't repost for this -- I'll make that change in ath/pending
I'd changed again on the request of another reviewer. Please feel free
to change as you like. I don't have any opinion on it.
>
> However, does ath12k need the same fix?
Looking at ath12k, there is similar code structure in
ath12k_qmi_alloc_chunk(). By adding some logging, we can confirm if
ath12k requires the fix or not. As a lot of code is similar in both
drivers, ath12k may require the same fix.
I don't have access to ath12k. So I cannot test on it.
> If so, can you post a separate patch for that?
>
> /jeff
--
Regards,
Usama
next prev parent reply other threads:[~2025-05-06 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 8:02 [PATCH v5] wifi: ath11k: Fix memory reuse logic Muhammad Usama Anjum
2025-04-29 2:39 ` Baochen Qiang
2025-05-05 8:11 ` Muhammad Usama Anjum
2025-05-05 19:17 ` Jeff Johnson
2025-05-06 6:41 ` Baochen Qiang
2025-05-06 6:43 ` Baochen Qiang
2025-05-06 14:42 ` Jeff Johnson
2025-05-06 13:10 ` Muhammad Usama Anjum [this message]
2025-05-06 14:37 ` Jeff Johnson
2025-05-07 2:12 ` Baochen Qiang
2025-05-16 18:33 ` 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=ec0bb100-4a70-4827-86b1-e4a7e8867a2d@collabora.com \
--to=usama.anjum@collabora.com \
--cc=ath11k@lists.infradead.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_bqiang@quicinc.com \
/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