linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mario Limonciello <superm1@kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	Matthew Schwartz <matthew.schwartz@linux.dev>,
	Linux kernel regressions list <regressions@lists.linux.dev>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: 6.14.y regression in ath11k
Date: Thu, 17 Apr 2025 16:06:46 +0200	[thread overview]
Message-ID: <2025041740-tableware-flight-b781@gregkh> (raw)
In-Reply-To: <cab8e07a-84fa-48f3-ac6f-382148b20744@kernel.org>

On Tue, Apr 15, 2025 at 05:11:04PM -0500, Mario Limonciello wrote:
> Hello,
> 
> Matt Schwartz (cc) found a regression in 6.14.2 that the Steam Deck OLED
> took 45s to find a network after suspend/resume waiting for a timeout.
> This was a regression from 6.14.1.
> 
> The regression happened because:
> 
> commit 933ab187e679 ("wifi: ath11k: update channel list in reg notifier
> instead reg worker")
> was backported to 6.14.y without the other commit in the series:
> 
> commit 02aae8e2f957 ("wifi: ath11k: update channel list in worker when wait
> flag is set")
> 
> Backporting commit 02aae8e2f957 ("wifi: ath11k: update channel list in
> worker when wait flag is set") to 6.14.2 fixes the regression.
> 
> Can you please take this commit back to stable too?

Now queued up, thanks.

greg k-h

      parent reply	other threads:[~2025-04-17 14:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 22:11 6.14.y regression in ath11k Mario Limonciello
2025-04-16  5:16 ` Jiri Slaby
2025-04-17 14:06 ` Greg KH [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=2025041740-tableware-flight-b781@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=matthew.schwartz@linux.dev \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=superm1@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).