public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: ath11k@lists.infradead.org,
	Reshma Immaculate Rajkumar <reshma.rajkumar@oss.qualcomm.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH ath-next v3] wifi: ath11k: Pass the correct value of each TID during a stop AMPDU session
Date: Tue, 24 Mar 2026 06:46:28 -0700	[thread overview]
Message-ID: <177435998825.2954589.4435953156706637235.b4-ty@oss.qualcomm.com> (raw)
In-Reply-To: <20260319065608.2408179-1-reshma.rajkumar@oss.qualcomm.com>


On Thu, 19 Mar 2026 12:26:08 +0530, Reshma Immaculate Rajkumar wrote:
> During ongoing traffic, a request to stop an AMPDU session
> for one TID could incorrectly affect other active sessions.
> This can happen because an incorrect TID reference would be
> passed when updating the BA session state, causing the wrong
> session to be stopped. As a result, the affected session would
> be reduced to a minimal BA size, leading to a noticeable
> throughput degradation.
> 
> [...]

Applied, thanks!

[1/1] wifi: ath11k: Pass the correct value of each TID during a stop AMPDU session
      commit: e225b36f83d7926c1f2035923bb0359d851fdb73

Best regards,
-- 
Jeff Johnson <jeff.johnson@oss.qualcomm.com>


      parent reply	other threads:[~2026-03-24 13:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-19  6:56 [PATCH ath-next v3] wifi: ath11k: Pass the correct value of each TID during a stop AMPDU session Reshma Immaculate Rajkumar
2026-03-23 16:01 ` Vasanthakumar Thiagarajan
2026-03-24  3:26 ` Baochen Qiang
2026-03-24 13:46 ` Jeff Johnson [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=177435998825.2954589.4435953156706637235.b4-ty@oss.qualcomm.com \
    --to=jeff.johnson@oss.qualcomm.com \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reshma.rajkumar@oss.qualcomm.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