public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Baochen Qiang <quic_bqiang@quicinc.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
	Muhammad Usama Anjum <usama.anjum@collabora.com>,
	Jeff Johnson <jjohnson@kernel.org>
Cc: <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 14:41:12 +0800	[thread overview]
Message-ID: <b7d0e180-c638-41fc-83c8-b21f623f8db9@quicinc.com> (raw)
In-Reply-To: <f58075f7-f643-4e47-b774-dc529aaa01e5@oss.qualcomm.com>



On 5/6/2025 3: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

Regarding this specific comment:

This change it to refine the QMI memory reuse logic, it is not related to any MHI target
memory.

Actually Muhammad changed the subject according to your comment in v3, but changed it back
based on my above comment in v5.

> 
> But don't repost for this -- I'll make that change in ath/pending
> 
> However, does ath12k need the same fix?
> If so, can you post a separate patch for that?
> 
> /jeff


  reply	other threads:[~2025-05-06  6:41 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 [this message]
2025-05-06  6:43   ` Baochen Qiang
2025-05-06 14:42     ` Jeff Johnson
2025-05-06 13:10   ` Muhammad Usama Anjum
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=b7d0e180-c638-41fc-83c8-b21f623f8db9@quicinc.com \
    --to=quic_bqiang@quicinc.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=usama.anjum@collabora.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