public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Johnson <jjohnson@kernel.org>
To: Thorsten Leemhuis <linux@leemhuis.info>,
	Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
	Jeff Johnson <jjohnson@kernel.org>
Cc: linux-wireless@vger.kernel.org, ath12k@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: [PATCH ath-current] wifi: ath12k: prepare REO update element only for primary link
Date: Wed, 22 Apr 2026 07:34:18 -0700	[thread overview]
Message-ID: <0bb445e0-658f-47e1-a455-7fc4513c8fb0@kernel.org> (raw)
In-Reply-To: <ed0ecf21-54b4-41e0-92a9-3c7a0e140882@leemhuis.info>

On 4/22/2026 2:30 AM, Thorsten Leemhuis wrote:
> Lo! Top-posting on purpose to make this easy to process.
> 
> Jeff, what happened to below patch? It was supposed to fix the
> regression linked below, but unless I'm missing something (which might
> very well be the case!) it seems it never got any further than this thread.
> 
> Ciao, Thorsten
> 
> P.S:: Adding a stable tag might be good to ensure this fix is backported.

No, I dropped the ball on this. Let me pick it up for next week's -rc2

/jeff


  reply	other threads:[~2026-04-22 14:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10  3:07 [PATCH ath-current] wifi: ath12k: prepare REO update element only for primary link Baochen Qiang
2026-03-19  3:46 ` Vasanthakumar Thiagarajan
2026-03-19 14:14   ` Jeff Johnson
2026-03-19 16:23     ` Vasanthakumar Thiagarajan
2026-04-22  9:30 ` Thorsten Leemhuis
2026-04-22 14:34   ` Jeff Johnson [this message]
2026-04-23 18:00 ` 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=0bb445e0-658f-47e1-a455-7fc4513c8fb0@kernel.org \
    --to=jjohnson@kernel.org \
    --cc=ath12k@lists.infradead.org \
    --cc=baochen.qiang@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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