From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: "Alex G." <mr.nuke.me@gmail.com>,
ath11k@lists.infradead.org, Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] wifi: ath11k: move .max_tx_ring to struct ath11k_hw_hal_params
Date: Thu, 25 Dec 2025 17:53:46 +0800 [thread overview]
Message-ID: <566f4d26-8a36-415b-9ec7-3dc5082acb2b@oss.qualcomm.com> (raw)
In-Reply-To: <3484871.yKVeVyVuyW@nukework.gtech>
On 12/25/2025 5:53 AM, Alex G. wrote:
>
> Sure, I will do it this way.
>
> I am ready to submit the IPQ9574 support, and this patch is a dependency.
> Should I include v3 of this patch in the IPQ9574 series, or submit v3
> independently?
>
> Alex
>
I would suggest a v3 for track purpose. Another reason is that this patch is more of an
optimization benefiting all chips, rather than being specific to your new chip.
prev parent reply other threads:[~2025-12-25 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 4:35 [PATCH v2] wifi: ath11k: move .max_tx_ring to struct ath11k_hw_hal_params Alexandru Gagniuc
2025-12-16 7:14 ` Baochen Qiang
2025-12-24 21:53 ` Alex G.
2025-12-25 9:53 ` Baochen Qiang [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=566f4d26-8a36-415b-9ec7-3dc5082acb2b@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mr.nuke.me@gmail.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