ATH11K Archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
	 Greg KH <gregkh@linuxfoundation.org>,
	 Sasha Levin <sashal@kernel.org>,
	 Linux kernel regressions list <regressions@lists.linux.dev>,
	 LKML <linux-kernel@vger.kernel.org>,
	 netdev <netdev@vger.kernel.org>,
	Benjamin Berg <benjamin.berg@intel.com>,
	linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: Consider picking up "tpm: Enable hwrng only for Pluton on AMD CPUs" rather sooner than later
Date: Fri, 26 Jan 2024 08:06:58 +0200	[thread overview]
Message-ID: <87mssszkzh.fsf@kernel.org> (raw)
In-Reply-To: <3bfb5c07-664e-49cd-a470-635a36bcf806@leemhuis.info> (Thorsten Leemhuis's message of "Fri, 26 Jan 2024 07:02:43 +0100")

+ linux-wireless, ath11k

Thorsten Leemhuis <regressions@leemhuis.info> writes:

> Hi stable team, JFYI, yesterdays mainline commit 556857aa1d0855 ("wifi:
> ath11k: rely on mac80211 debugfs handling for vif") from Benjamin
> contains no stable tag, but a Fixes: tag for a 6.7 commit. So it guess
> you will pick it up anyway. Might be worth picking up rather sooner than
> later, as it fixes a regression that according to Kalle causes ath11k to
> crash during suspend:
> https://lore.kernel.org/all/874jfjiolh.fsf@kernel.org/
> https://bugzilla.kernel.org/show_bug.cgi?id=218364

Thanks. The subject doesn't match the body but I guess that's just a
copypaste error :)

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches


           reply	other threads:[~2024-01-26  6:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <3bfb5c07-664e-49cd-a470-635a36bcf806@leemhuis.info>]

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=87mssszkzh.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=ath11k@lists.infradead.org \
    --cc=benjamin.berg@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.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 read-only IMAP folder(s) and NNTP newsgroup(s).