archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: Felix Fietkau <>,
	Lorenzo Bianconi <>,
	Ryder Lee <>,
	Shayne Chen <>,
	Sean Wang <>
Cc: XiaoYan Li <>,
	LKML <>,
	"" <>,
	Johannes Berg <>,
	Kalle Valo <>,
	"" <>
Subject: [Regression] Bug 216421 - [regression] nl80211: kernel reports: key addition failed
Date: Sun, 28 Aug 2022 13:22:17 +0200	[thread overview]
Message-ID: <> (raw)

Hi, this is your Linux kernel regression tracker speaking.

I noticed a regression report in As many (most?)
kernel developer don't keep an eye on it, I decided to forward it:

>  XiaoYan Li 2022-08-27 12:40:07 UTC
> This is a regression. It doesn't happen on 6.0-rc.1 or 5.19 kernel.
> Network card: MEDIATEK MT7922 802.11ax
> ---
> wpa_supplicant: nl80211: kernel reports: key addition failed
> wpa_supplicant: TDLS: Failed to set TPK to the driver
See the ticket for more details.

I'd also like to add the report to the list of tracked regressions to
ensure it's doesn't fall through the cracks in the end:

#regzbot introduced: v6.0-rc1..v6.0-rc2
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

             reply	other threads:[~2022-08-28 11:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28 11:22 Thorsten Leemhuis [this message]
2022-09-13  4:56 ` [Regression] Bug 216421 - [regression] nl80211: kernel reports: key addition failed #forregzbot Thorsten Leemhuis

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).