linux-kernel - Re: [REGRESSION] MT7915E doesn't work any more with v6.9

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <98871a58e675aef7ad7f2e5bd3bb2ee526d29d5f.camel@sipsolutions.net>
Date: Mon, 27 May 2024 20:30:31 +0200
From: Johannes Berg <johannes@...solutions.net>
To: Greg KH <gregkh@...uxfoundation.org>, Kalle Valo <kvalo@...nel.org>
Cc: Oleksandr Natalenko <oleksandr@...alenko.name>, 
 linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org, "Linux
 regression tracking (Thorsten Leemhuis)" <regressions@...mhuis.info>,
 linux-mediatek@...ts.infradead.org,  linux-arm-kernel@...ts.infradead.org,
 Felix Fietkau <nbd@....name>, Lorenzo Bianconi <lorenzo@...nel.org>, Ryder
 Lee <ryder.lee@...iatek.com>, Shayne Chen <shayne.chen@...iatek.com>, Sean
 Wang <sean.wang@...iatek.com>, Matthias Brugger <matthias.bgg@...il.com>,
 AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, Peter
 Chiu <chui-hao.chiu@...iatek.com>, StanleyYP Wang
 <StanleyYP.Wang@...iatek.com>,  Linux regressions mailing list
 <regressions@...ts.linux.dev>
Subject: Re: [REGRESSION] MT7915E doesn't work any more with v6.9

On Mon, 2024-05-27 at 20:29 +0200, Greg KH wrote:
> > 
> > Yeah, commit 2f7cf3b61d85 should have been taken to wireless tree but it
> > fell through the cracks. I didn't realise that it's an important bugfix
> > and the commit message didn't give any indication of that either.
> > 
> > But commit 2f7cf3b61d85 is now in Linus' tree so it would be good if
> > someone could submit it to stable releases.
> 
> It's already in 6.9.1, does it need to go anywhere else?
> 

No, but apparently we need a similar commit for mt7915e or something? I
have no idea why I missed those. I'll take a look tomorrow.

johannes