Re: [REGRESSION] iwlwifi: suspend failure, bisected

[Chris Bainbridge <chris.bainbridge@gmail.com>]

On Wed, Jul 16, 2025 at 01:50:57PM -0500, Bjorn Helgaas wrote:
> On Sat, May 31, 2025 at 03:09:35PM +0100, Chris Bainbridge wrote:
> > Hi,
> > 
> > There is a recently introduced iwlwifi regression on suspend. It appears
> > the bisected commit was only supposed to fix a warning, but reverting
> > the commit (with a small change for revert conflict) does fix the error.
> > 
> > 7438843df8cf7a484303caee7540a00f0ef972b2 is the first bad commit
> > Gustavo A. R. Silva <gustavoars@kernel.org>commit 7438843df8cf7a484303caee7540a00f0ef972b2
> > Author: Gustavo A. R. Silva <gustavoars@kernel.org>
> > Date:   Wed Mar 26 18:04:02 2025 -0600
> > 
> >     wifi: iwlwifi: mvm: Avoid -Wflex-array-member-not-at-end warning
> 
> https://git.kernel.org/linus/264c844abb29 ("wifi: iwlwifi: mvm: fix
> assert on suspend") appeared in v6.16-rc1 and includes a Fixes: tag
> for 7438843df8cf.
> 
> 264c844abb29 is not exactly the same as the patch Miri posted at
> https://lore.kernel.org/r/DM3PPF63A6024A9ECC64ACBA27CCABBAB0FA360A@DM3PPF63A6024A9.namprd11.prod.outlook.com,
> but maybe it still fixes this regression?
> 
> If so, can somebody send the appropriate regzbot fix command to remove
> this regression from the tracker
> (https://linux-regtracking.leemhuis.info/regzbot/mainline/)?
> 
> (See https://linux-regtracking.leemhuis.info/about/#tldr)
> 
> I feel like I might be missing something because there are several
> regressions in the tracker that *look* like they should have been
> resolved months ago.
> 
> Bjorn

#regzbot fix: 264c844abb29